Manual Testing class - 06

Environment:

It Is A Collection Of Resources, Like Hardware, Software And The Network Resources.

Architecture:

It Is The Interfaces Or Layers With Which A System(Software) Is Constructed.

There Are Different Architecture:

A) One Tier Architecture:

In This Case The Application And The Server Resides In The Same System.

These Are Generally Considered As Desktop Based Applications.

Ex: Ms Office, Windows Calculator, Media Player, Web Browsers..

Advantages:

1. They Are Fast And Reliable.

2. Security Is High.

Disadvantages:

1. Resources Cannot Be Shared In These Types Of Applications.

B) Two Tier Architecture:

In This The Server Is Split From The Client Machine And There Are Two Layers, Application/Business Layer

 And Database Layer

There Can Be Multiple Clients Connected To A Server Machine In A Network Generally With LAN(Local Area 

Network)

They Would Be Connected With A Topology Which Can Be Star, Bus, Mesh, Tree, Token Ring....

These Systems Are Often Called As Windows Based Applications Or Client/Server Applications

Ex: Oracle, Sql Server, Visual Source Safe...

Advantages:

1. Sharing Of Server Resources Is Improved.

2. Performance Is Good.

3. Security Is Good As No New Terminal Would Be Accessing The Server

Disadvantages:

1. Larger Networks Are Not Possible

2. The Complete Network Is Dependent On The Server Machine.

C) Three Tier Architecture:

These Are Latest Applications Where The Complete system Is Split Into Three Layers.

1) Interface Layer: First Layer Where The User Will Be Interacting With The Application

2) Middle Layer: This Is The Application Server Where The Application Logic Or Business Logic Is Present And 

Which Works As An Interface Between The Front Layer And The Database Layer.

3) End Layer: Which Is A Database Layer.

In The Interface Layer, There Should Be A Client Program(Web Browser), Installed To Interact With The 

Application, All The Requests Would Be Sent In The Form Of Http(Hyper Text Transfer Protocol).

To Process These Requests There Should Be A Web Server Installed, Which Acts As An Interface Between

 The Application Server And The Client.

Ex: Web servers:

      IIS(Internet Information Server)

      Tomcat, Apache, Web sphere,...

Advantages:

1. Sharing Of Resources Across The Networks

2. It Can Have Very Large Networks.

Disadvantages:

1. Security Is A Concern In Web Based    Applications

2. There Can Be Performance Issues In Web Based

D) N-Tier Architecture:

It Is An Extension To The Web Based Application, Having Multiple Apps Servers And The Database Servers To 

Balance The Increasing Loads.

-------------------------------------------------------

There Can Be Three Environments For Any Given Application:

1) Production Environment:

This Is Otherwise Called As Live Or Client Or Customer Environment, Which Is The Regional Environment Based on Which Two Other Environments Are Created

2) Development Environment:

The Environment That Is Created With The Same Set Of Resources Of The Customer Environment(Which Is Closely Simulated To Customer Environment), For The Development Activates.

3) Test Environment:

Otherwise Called As Demo Or Stage Or QA Environment, Which Is Also A Closely Simulated Environment To The Production Environment, Where The Testing Activities Are Carried Out.

Deployment:

The Process Of Moving The Build From Development Environment To The Test Environment For Further Testing.

Development Team Is Responsible For Developing The Build And Also For The Deployment Process.

Note: Test Lead Might Be Part Of The Deployment Process.

Deployment For Desktop/Client-Server Based Applications:

In This Case The Application Code Is Converted Into An Executable File And The Setup File Be Placed In The Project Server Of Test Environment, Where The Test Engineers Will Access And Install The Application In Every Individual Machine.

Deliverables:

SRN(Software Release Notes)

DD(Deployment Document)

Installation Document

Unit Test Report

Deployment For Web Based Applications:

The Application Logic/Source Doc(Files) Will Be Merged In The Apps Server Of The Test Environment Form 

The Development Environment.

The Test Team Will Access The Application Based on The "Url" That Is Provided By The Deployment Team.

Deliverables:

SRN(Software Release Notes)

DD(Deployment Document)

Unit Test Report

----------------------------------------------------------

Test Environment Set Up:

Setup Of The Hardware And Software Needs By The Test Team To Accept The Build For Further Testing.

As Part Of This Testing Team Have To Ensure The Software Requirements Like O/S, Browsers, Databases, 

Other Tools And The Access Privileges To All The Servers.

Test Execution Plan Has To be Prepared By The Test Lead On The Build That Is Deployed, Like Planning Of 

Resources, Time Required, Features To be Tested And The Template Or Rafts For The Test Execution Reports.

Test Set: It Is A Collection Of Test Cases, Which Has To Be Done, Based On The Build That Is Deployed For 

Testing.

Test Plan:

It Is A Planning Document That Is Prepared At Very initial Stage Of The Test Process Implementation.

A Test Plan Defines The Scope For Testing, Objective, Resources Required, Timelines To be Followed Along 

With The Test Management Documentation.

Test Plan Is Generally Prepared By The Experienced Person Or Team Like Test Lead, Analyst Or Test Manager.

The Inputs Required For Test Plan Are Requirements And Project Plan.

This Can Be Drafted In A Word Document Which Should Approved Prior To Implementation Of Any Test Activity

 In A Given Project.

Contents of Test Plan:

1.0 Objective

2.0 Scope

                        2.1 In-Scope

                                                - Features To Be Tested

                        2.2 Out Scope

                                                - Features Not To Be Tested

3.0 Approach

                        3.1 Test Analysis Approach

                        3.2 Test Design Approach

                        3.3 Test Execution Approach

                        3.4 Test Management Approach

4.0 Resources

                        4.1 Hard Ware Resources

                        4.2 Software Resources

                        4.3 Human Resources

                                    Ex :

                                               

Id	Resource	Role
1	Ramesh	TM
2	Suresh	TL
3	Kiran	TE

  

5.0 Schedules

                                   

Id	Task Item	Responsible	Planned Hours
1	TC Design For Login	Suresh
2	TC Execution For Login	Kiran
-- --	------- -------	------- -------	------- -------

6.0 Risks & Mitigation (Solution)

                                   

Id	Risk	Mitigation
1	Resources May Take Off / Leave Organization	Minimum 30% Bench Resources Should Be Available
2	Resource May Not Have Sufficient Knowledge On Project Domain	They Should Be Taken Training Sessions .
-- --	------- -------	------- -------

7.0 Entry Criteria & Exit Criteria

                        7.1  Entry Criteria

                                    Ex ( Entry Criteria For System Testing )

                                                1) 100% Unit And Integration Testing Should Be Success Full

                                                2) All Customer Requirements Should Be Based Line.

                                                3) TC Prepared Should Be Review And Approved.

                        7.2  Exit Criteria

                                    Ex ( Exit Criteria For System Testing )

                                                1) All Major Defects Should be Fixed And Closed.

                                                2) All Test Cases Should Be Executed successful And Passed