testing tools manual

8/8/2019 Testing Tools Manual

http://slidepdf.com/reader/full/testing-tools-manual 1/66

[email protected] Suresh.B – 9440163282

Manual Testing 1

Jai Sri Ram Jai Sai RamQuality

Quality means satisfaction of the customer.To define good quality of software, the company people will concentrate

on two (2) factors such as 1) Technical factor and 2) Non-technical factor.1) Technical factor a. Customer requirements in terms of functionalities.

b. Customer expectations (Look and feel, Ease of use, right output,speed of processing, security)

2) Non-technical factor a. Low cost to purchase

b. Time to market.

S.Q.A (Software Quality Assurance)It means monitoring and measuring the strength of development process.

REQUIREMENTS GATHERINGSBusiness Development People / Business Analyst

Business Requirement Specification (BRS) / User Requirement Specification (URS) / Customer Re uirement S eci ication CRS

ANALYSISAnalyst

Software Requirement Specification (S/W RS)

FRS Functional Requirement

S eci ication

SRSSystem Requirement

Specification

DESIGNDesigners

Design Document LLD Low Level Design Document

HLD High Level Design Document

CODING

Programmers

TESTINGTesters

PROJECT MANAGEMENTRelease and Maintenance



Suresh.B – 9440163282 [email protected]

2 Manual Testing

1) R EQUIREMENT G ATHERINGS :In general software development starts with requirement gathering. In

this stage Business Development People (BDP) / Business Analyst People (BA)are preparing Business Requirement Specification Document (BRS) / User Requirement Specification Document (URS) / Customer RequirementSpecification Document (CRS), after gathering all required requirements fromthe user / customer.

Business Requirement Specification Document defines the requirementof the customer.

2) ANALYSIS :After completion of Business Requirement Specification Document,

Analyst People are preparing “Analysis Document”. This document is alsocalled as “Software Requirement Specification Document” (S/w RS). Thedocument consists of (2) Sub documents such as FRS & SRS

(i) FRSIt means “Function Requirement Specification”. It defines

the required functionality to be used in the project.(ii) SRS

It means “System Requirement Specification”. It defines therequired Hardware to develop that functionality.

3) DESIGN After completion of Analysis Document, Designers are preparing Design

Document. It consists of (2) sub documents, such as (i) HLD & (ii) LLD(i) HLD (High Level Design Document)

It is also called as External Design Document. It defines thehierarchy of over all application functionalities in terms of modulesfrom root level to leaf level.

Ex:

Mail Chat

Login

Logout




Manual Testing 3

(ii) LLD (Low Level Design Document)It is also known as Internal Design Document. It defines the

internal logic of every functionality or module in terms of ER Diagrams, Data Flow Diagrams.

4) C ODING : A Physical construction of Software is called as “Coding”.

Build: An executable form of all integrated module set is called “Build”.

5) T ESTING

In this stage, the testers are validating that developed Build withrespective Customer requirements and customer expectations.

6) R ELEASE AND M AINTENANCE After completion of software testing the Project Management will

deliver that software to customer for usage.During utilization of the software, if customer get any problem or

if customer want to enhance the application, that can be handled by thecompany people.

System

M1 M2 M3

S2 S3S1

SS1 SS2 SS3

P3P2P1

LOGINUser NamePassword

V

V

OK CANCEL

DATABASE

V

IV

IV

V

IV

IV

V - Valid

IV - Invalid

MESSAGE BOX

Please Try Again

OK

INBOX

Note: A Project will have one HLD and Multiple LLDs.

BUILD




4 Manual Testing

What is the difference between Software Product and SoftwareApplication?

Software ApplicationIf the Software developed with respective particular client requirements

or single client requirements that can be called as Software Application.Ex: Bank Applications, Hospital Applications.

Software ProductIf the Software developed with respective multiple clients requirements,

that can be called as Software Product.Ex: MS Office, VB, Operating System etc.,

What is Error, Defect, Bug?

Error: Any mistake in a programme is called “Error”.

Defect:Any mistake found by the tester during Testing can be called as “Defect”.

Bug:The reported defect is accepted by developer to resolve can be called as

“Bug”.

SQC (Software Quality Control)It is a process of validating the Software.

Why Software has Bugs?(i) Poor requirements(ii) Futurities (Customers requirements are frequently changing)(iii) Miscellaneous Communication.(iv) Unrealistic schedule(v) Inadequate testing.Solutions(i) Solid requirements(ii) Good communication(iii) Realistic schedule(iv) Adequate testing(v) Gather / Stick to initial requirements as much as possible.




Manual Testing 5

TESTING MODELSF ISH M ODEL

Fish model defines the mapping between development stages and Testingstages.

Reviews in AnalysisIn general Software Development process starts with requirements

gathering and analysis. In this, Business Development People are preparing

Business Requirement Specification Document and Analyst people are preparing Analysis Document with respective to Business RequirementSpecification.

After completion of analysis document, the same category peopleconducting reviews in Analysis Document for completeness and correctness.

During the review they are concentrate on the below factors.i) Are they complete?ii) Are they right requirement?iii) Are they achievable?iv) Are they reasonable?v) Are they testable?

Reviews in Design DocumentAfter completion of Analysis document and corresponding reviews,

designers are preparing design document which includes FunctionalRequirement Specifications and System Requirement Specifications.

After completion of design document the same category people areconducting reviews in design document for completeness and correctness.

During the review they concentrate on below factors.

RequirementsGathering

BRS / CRS /URS

Reviews inAnalysis

S/W RS (FRS & SRS)Analysis

Reviews inDesign

Design(HLD & LLD) Coding

White Box Testing /Glass Box Testing /

Programe PhaseTesting / Open Box

Testing

Black BoxTesting /

Functional &System Testing

/ Close BoxTesting

Release &Maintenance

Test SoftwareChanges

Validation Verification




6 Manual Testing

i) Are they complete/ii) Are they met right requirements?iii) Are they understandable?iv) Does they handle Errors or not?

White Box TestingAfter completion of deign document and correspondence reviews, programs with concentrate on coding to construct a Software Build.

After completion of preparing all programs, Programmers areinterconnecting them to a system. In this interconnection of programs to verifythe programs and interface between programs or modules, programmers areconducting “White Box Testing”

White Box Testing classified as Two Types such as (I) Unit Testing(II) Integration Testing.

(I) Unit TestingIt is also called as Program Testing or Micro Testing. Unit testingmeans “Single Program Testing or Component Testing. Unit testingconsists of below factors.

a) Basic Path Testing.During this testing programmers are checking that whether

the program is running or not?To perform this test they will follow below approach.1) Draw flow diagram of that program.2) Calculate number of independent paths in that program

(Cyclometic Complexity) (The number of independent paths in the program)

3) Execute the program more that one time to cover allindependent paths in that program.

b) Control Structure Testing In this testing the programmers will concentrate on

corresponding program output.In this programmers will concentrate on every statement

including, If conditions, For loops, Memory allocation etc.,c) Program Technique Testing

In this testing the programmers are checking the executionspeed of the program.

If the execution speed of the program is not good, then programmers are performing changes in the structure of the program without disturbing functionality.

d) Mutation Testing Mutation means changes in a program. In this testing

programmers are performing wanted changes in the program and

executing the program repeatedly. In this Test repetition,




Manual Testing 7

Programmers are checking the completeness and correctness of theTest.

Passed Passed Failed(In-compete (Complete

Testing) Testing)(II) Integration Testing

After completion of dependent program development andcorresponding Unit Testing, Programmers are interconnecting to form

a system. To estimate the interface between programs or modules programmers are conducting Integration Testing. They are (4) Typesof approaches.a) Top-Down Approach.

The verification of main module without coming to some of the Sub-Modules is called as Top-Down Approach.

“Conduct test on Main module without conducting test onsome of the Sub-Modules is called Top-Down Approach.”

In the above approach “STUB” is a Temporary Program, itworks like as under constructive Sub Module, it is also called asCalled Program.

b) Bottom-Up Approach.The verification of Sub-Modules without coming from Main

Module is called “Bottom-Up” Approach.

“Conducting test on Sub-Modules without testing on MainModule is called Bottom-up Approach.

In the above approach “Driver” is temporary program, itworks like as under constructive Main Module. Driver is alsoknown as Calling Program.

Perform change

A=10B=20I=A+BC=Imsgbox I

A=10B=20C=A+Bmsgbox I

Main Module

Sub-Module-1 Sub-Module-2

STUB

Sub-Module-3

Main Module

Driver / Calling Program

Sub-Module-1 Sub-Module-2 Sub-Module-3

Temporary Program/ Called Program




8 Manual Testing

c) Hybrid Approach / Sand-witch Approach

The combination of Top-down Approach and Bottom-Up

Approach is called as Hybrid Approach / Sand-witch approach.

d) Bigbang Approach.The verification of all modules after completion of all

Modules development and corresponding unit testing is called as“Bigbang Approach”.

This approach is not suitable for large modules.

C ASE STUDY

Case 1: Top-down approach is followable, when the customer’s

requirements are constituent of clear.

Case 2: Bottom-up approach is followable, when the customer’s

requirements are not clear or frequently changing.

Case 3: Hybrid Approach is followable, when the customer’s requirements

are clear and the architecture structure of the system is changing.

Case 4: Bigbang Approach is followable, when the application build

consists less number of modules or less number of

interconnections.

Main Module

Driver / Calling Program

Sub-Module-1 Sub-Module-2 Sub-Module-3

Sub-Sub-Module-1

STUB

Sub-Sub-Module-2 Sub-Sub-Module-3

Bottom-UpApproach

Top-DownApproach




Manual Testing 9

BLACK BOX TESTINGAfter completion integration of all modules to form a system, developers

are sending that build to the separate Testing team. This separate testing teamvalidates the Software build with respective customer’s requirements andexpectations through “Black Box Testing” techniques.

It is also known as “Close Box Testing” / “Functional & System Testing”It is classified as (3) types such as

1) Usability Testing.a. User Interface Testing.b. Manual Support Testing.

2) Functional Testing.a. Functionality Testing.b. Sanitation Testing.

3) Non-Functional Testing.a. Recovery Testing.b. Compatibility Testing c. Configuration Testing.d. Intersystem Testing e. Comparative Testing

f. Security Testing. g. Installation Testing.h. Load Testing.

i. Stress Testing j. Data Volume Testing.k. Storage Testing.

1) Usability TestingAfter receiving build from the development people, testers are conducting

usability testing to check whether the application build is providing user friendly screens or not.

Usability Testing is classified into (2) Types such as (a) User InterfaceTesting (2) Manual Support Testing.

a. User Interface TestingDuring this testing testers are checking the Look and Feel, Ease of

use of application of build screen.Ex: The Microsoft (6) Rules for testing1) Controls are initcaps.2) Ok, Cancel existence.3) System Menu existence.4) Controls are not overlapped.5) Controls should be visible.6) Controls must be aligned.




10 Manual Testing

b. Manual Support TestingIt is also known as “Help document Testing”. During this testing

Testers are checking the context sensitiveness testing.Ex: Spelling Mistakes, Grammar mistakes, Word Missing, Line

Missing etc.,Case 1: Receive build from the developers. User interface testing. Functional & Non-Functional Testing Manual Support Testing.

2) Functional TestingAfter completion of User Interface testing, Testers are conducting

Functional Testing to validate customer requirements.Functional Testing classified into (2) Types (a) Functionality

Testing (b) Sanitation Testing.a) Functionality Testing

During this Testing Testers are validating customersrequirement in terms of (6) coverage.1) Behavioural Coverage.2) Input Domain Coverage.3) Error-Handling Coverage.4) Calculation Coverage.5) Back-end Coverage.

6) Service level Coverage.1) Behavioural Coverage.In this testing Testers are checking whether the objects are properly

responding of not, with respective to Business Operation.2) Input Domain Coverage

In this testing Testers are checking whether the input objects /Input fields are taking right type and range of value or not.

To perform this test we (Testers) are using (2) Types of Testing.(i) BVA (Boundary Value Analysis(ii) ECP (Equivalence Class Partitioning)

BVA(Range of Object)

ECP(Defines Type of Object)

Range Expected Actual Result Valid InvalidMin=Min-1=Min+1=Max=Max-1=Max+1=

PassFailPassPassPassFail

Pass fail

UsabilityTesting




Manual Testing 11

Ex: A Login process allows User Name and Password from a User. In thisUser Name object allows “Alphabets lower case” Range from 4 to 8Characters long and Password object allows “Alphabets lower case”range from 6 to 10 Characters long.

Prepare BVA and ECP for the above expected.

BVA & ECP for User NameBVA ECP

Range Expected Actual Result Valid InvalidMin= 4 Char Min-1= 3 Char Min+1= 5 Char Max= 8 Char

Max-1= 7 Char Max+1= 9 Char

PassFailPassPass

PassFail

[a-z] [A-Z][0-9]All

Special

characters

BVA & ECP for PasswordBVA ECP

Range Expected Actual Result Valid InvalidMin= 6 Char Min-1= 5 Char Min+1= 7 Char Max= 10 Char Max-1= 9 Char Max+1= 11 Char


[a-z] [A-Z][0-9]All

Specialcharacters

Ex: Age object allows numeric range from 16 to 60.Prepare BVA and ECP for the above expected.

BVA & ECP for AgeBVA ECP

Range Expected Actual Result Valid InvalidMin= 16Min-1= 15Min+1= 17Max= 60Max-1= 59Max+1= 61


[0-9] [A-Z][a-z]All

Specialcharacters




12 Manual Testing

Ex: Mobile No. object allows numeric 10digits only. Prepare BVA and ECP for the above expected.

BVA & ECP for Mobile No.BVA ECP

Range Expected Actual Result Valid InvalidMax= 10Max-1= 9Max+1= 11

PassFailFail

[0-9] [A-Z][a-z]

All Special characters

3) Error-Handling Coverage.In this we are checking whether the objects are preventing“Negative Operations” or not.

4) Calculation Coverage.

In this we are checking whether thefunctionality output is right or wrong.

5) Back-End Coverage.

ODBCJDBC

In this testing we are checking whether the insert of front endoperations on back end table context.

6) Service level coverage.The order functionality.




Manual Testing 13

b) Sanitation TestingIt is also known as “Garbage Testing”. During this testing,

testers are finding extra functionalities in the build with respect tocustomer requirements.

3) Non-Functional Testing

After completion of Functional Testing, testers are concentratingon Non-Functional Testing to validate extra characteristics of that build.They are divided into (11) Types.

a) Recovery TestingDuring this testing we are checking that whether the application

Build is changing from Abnormal State (Crash / Hang) to Normal State or not.

Abnormal State to Normal State

Normal State

Abnormal State

b) Compatibility TestingThey are (2) types of Compatibility Testing.

V.B Unix VC++ Win98

Ex: Unix does not support VB Win98 is supporting VC++Techniques But Build is not working

Properly due to defectsDuring this testing we are checking whether the application build is

able to run on different platforms or not.Platform means Operating System, Browsers, compilers and other

System software’s.

Build

O.S

Build

O.S




14 Manual Testing

c) Configuration TestingIt is also known as “Hardware Compatibility Testing”. During this

testing we are validating whether the application build is supportingdifferent technologies input / Output devises or not.

d) Intersystem Testing.It is also known as “Inter operability Testing”. During this testingwe are checking whether the application build is coexistence with other existence to share common resource or not.

Ex.: E-Seva.

e) Comparative Testing.It is also known as “Competitive Testing”. During this testing we

are comparing the features of produce with some like previous produce(or) Existing produce in the market to estimate competitiveness.

f) Security Testing.It is also known as “Penetration Testing”. During this testing we

are validating (3) types of factors such as(i) Authorization.(ii) Access Control.(iii) Encrypt / Decrypt Data Testing.

(i) Authorization.In this testers are checking whether a valid user is accessible

or not, invalid user is preventable or not.(ii) Access Control

In this we are checking whether a valid user have permissionto use specific features / Services or not.

Common DataBase

Server

Server Elec. Bill

Telephone Bill

Water Tax Bill

Income Tax Bill

Municipal Bill Server

Server

Server

Note: Comparative Testing is applicable for Software Produces onlynot for applications, because Software application is developedfor a single client requirement, but product can be developed withrespect to multiple clients requirements.




Manual Testing 15

(iii) Encrypt / Decrypt Data Testing.The code conversion in between client process and server

process to avoid third party accessing.

g) Installation TestingIt is also known as “Deploying Testing”. During this testing we

are validating below factors.

h) Load Testing.Run the application under customer expected configuration under

customer load to estimate the speed of processing is called “LoadTesting”.

i) Stress Testing.Run the application under customer expected configuration under

various loads from low to peak to estimate Stress capacity of theapplication build is called Stress Testing.

j) Storage Testing.The execution of application build under customer expected

configuration under huge amount of resources to estimate the storagecapacity of the application database is called Storage Testing.

k) Data Volume Testing.During this testing Testers are calculating the number of records to

be stored into application database.

CLIENTUser Name

Password SERVER

RequestEncrypt

Cipher Text

Cipher Text

Decrypt

Request

Encrypt

Decrypt

Build& Supported

Software

Customer expectedconfigureComputer

Setup Program.Easy Navigation.Occupied Disk Space.Check Un-installation.

Note: Storage Testing, Data volume Testing coverages same, but StorageTesting is representing in Number of bytes and Data Volume Testing

is representing number of Records.




16 Manual Testing

GRAY BOX TESTING

Gray Box Testing is a combination of “White Box Testing” andBlack Box Testing.

UAT (User Acceptance Test)

After completion of Software Testing, the Project Management / Project

Manager will invite customer to collect feedback on one developed software.

They are (2) types such as

α – Test(Alfa Test)

β – Test(Beta Test)

Software Application.By Real customer.At development site.

Software Product.By Model customer.At customer site.

Release Testing

It is also known as “Port Testing”. After completion of User AcceptanceTest” and corresponding modifications, the Project Management will establishRelease Team with few Developers, few Testers and One (or) two Hardware

Engineers. This release team will go to customer’s site to install the softwareion the customer’s environment.

During this they will concentrate on below factors. Compact Installation. Overall functionality. Input device handling. Output device handling. OS Error handling.

Secondary storage handling. Coexistence with other existence software.

After completion of above like factor observation the release team is providing required training sessions to the customers to understand about the project.




Manual Testing 17

MaintenanceDuring utilization of Software by customers, the company people are

receiving change request from them.To receive change request from the customers the Project Management

establish “CCB” (Change Control Board) with few Developers, few testers andProject Manager.

CASE STUDYT ESTING STAGES R ESPONSIBLE P ERSONS

Review in Analysis AnalystReview in Design Designer Unit Testing ProgrammersIntegration Testing ProgrammersFunctional & System Testing Test Engineers / TestersUser Acceptance Testing Users / CustomersRelease Testing / Port Testing CCB

T ERMINOLOGY DEVELOPERS T ESTERS

Input Test DataOutput Test LogProgram Test Script

Challenges in TestingGenerally organizations are maintaining separate Testing for Functional

and System Testing. This separate Testing team is also involving in ReleaseTeam and CCB. Some time this separate Testing team is also not able toconduct planned Testing or good testing due to some risks.

CCB

Receive change

Enhancement Missed Defect

Impact Analysis

Perform changes

Test S/w changes

Impact Analysis

Perform changes

Test S/w changes

Increase Testingprocess Capability




18 Manual Testing

The risks are Lack of knowledge on project domain. Lack of communication. Lack of resources.

Lack of time. Lack of Test Data.To overcome above like risks, the people are following “Ad-hoc”

Testing.

Planned TestingA Tester conduct Test on application build with pre-planned procedure is

called Planned Testing .(or)

A Tester conduct Test on application build by following formal methodsare called Planned Testing .

Ad-hoc TestingA Tester conduct test on application build without Pre-planed is called

Ad-hoc Testing .(or)

A Tester conduct test on application build by following “InformalMethods” is called “ Ad-hoc Testing ”.

They are classified as (4) Types.(a) Monkey Testing.

Due to lack of time, Testers are conducting test on major functionalities of the application build. This style of testing is called“Monkey Testing ”. It is also known as Cheapening Testing.

(b) Buddy Testing.Due lack of time, Testers are grouping with programmers to

conduct Test on application as early as possible. This style of Testing iscalled as Buddy Testing .

Buddy means a group of Programmers and Testers.(c) Pair Testing.

Due to lack of knowledge on domain Junior Testers grouped withSenior Testers to share their knowledge. This style of testing is calledPair Testing .

(d) Exploratory Testing .Due to lack of Test Data, Testers are conducting Test on

application depending on available documents, discussions with other andget the requirements from customers. This style of testing calledExploratory Testing .




Manual Testing 19

SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)1) W ATERFALL M ODEL

In this Model next stage starts after completion of previous stage. There is no overlapping between two stages.

ADVANTAGES i) It is less expensive.ii) It works well for small applications.iii) It is flexible when the customer requirements are constant.

DISADVANTAGES i) Testing is a single stage starts after coding.ii) If any defect is found during Testing, the rectification of that defect

would be difficult.iii) It is “not flexible” to have changes in the customer requirements during

developing the software.

2) INCREMENTAL W ATERFALL M ODEL To overcome some of the limitations of Waterfall we can use IncrementalWaterfall model. Incremental Waterfall Model can be used Software ProduceDevelopment.

In this Model a set of requirements they would be one working product.

Requirement Gathering

Analysis

Design

Coding

Testing

Release &Maintenance

R.G Analysis Design Coding Testing R & M



1.0

2.0

3.0




20 Manual Testing

3) P ROTOTYPE M ODEL It is followable when the customer requirements are not clear.“Prototype means a sample Model of application without

functionality.

ADVANTAGES i) It is flexible when the customer requirements are not clear.

DISADVANTAGES i) It is expensive

4) Spiral Model Spiral Model is followable when the customer requirements areenhanceble in terms of versions. In this Model we will start the process within complete requirements.

ADVANTAGES It is flexible for high risk based projects.

DISADVANTAGES It is expensive.

Not Clear

Hardware Prototype Software Prototype

Demo to Client

Requirements refinedFinalize Environment

BRS Base linedSRS Base lined

1.0 2.0 3.0 4.0 5.0

Planning Risk Analysis

RequirementGathering

EngineersEvaluation

Coding andTesting

CustomerEvaluation




22 Manual Testing

6) Agile Model It is a latest model which is used in Software produce development. In this model we can get build from the developers in very short time (1to 4 Weeks)

In this model development process, testing process will be carried out parallelly.

They are (2) methods such as(a) X-Tream Programming.(b) Scrum

ADVANTAGES i) Any defect identified early, so that he rectification of the defect cost

and time would be very less.

ii) As the defect is identified early, the impact of the same defect is veryless on subsequent features.

DISADVANTAGES i) Documentation is very less.

Sanity TestingAfter receiving the build from the developers we people are conducting

“Sanity Testing” to estimate stability of that build before start real testing.During this testing we will be concentrate on below factors.a) Understandable.

b) Operatable.c) Observable.d) Controllable.e) Consistency.f) Automatable.g) Maintainableh) Simplicity.

From the above (8) factors, Sanity Testing is also known as BuildVerification Testing (BVT) or Tester Acceptance Testing (TAT) or TestabilityTesting or Oct-angle Testing.

Smoke TestingLike as Sanity Testing, Smoke Testing is also used to estimate the

stability of the Build.




Manual Testing 23

Re-Testing.Case 1: The repeating of same test for more than one time with multiple

data is called as “Re-Testing”.Case 2: The re-execution of failed tests on modified build to ensure bug

fixing work is called “Re-Testing”

Regression Testing.The Re-execution of selected test or modified build, to check is there any

side effects occurred or not on dependent functionalities by modifying reporteddefects or by adding new requirements.

Types of BuildThey are (7) types of Build. They are

(1) Initial Build

(2) Stable Build

(3) Defect effected Build

(4) Modified Build

(5) Complete Build

(6) Master Build

(7) Golden Build

Types of ProjectsMainly there are (3) Types of projects. They are (1) Traditional Project

(2) Outsourcing Project (3) Maintenance ProjectType of Project R/G Analysis Design Coding Testing R&M

Traditional

Outsourcing

Maintenance

Development Initial BuildSanityTesting

Comprehensive Testing Bug

Fixing

Re-TestingRegression

Testing Test Closer (Test Lead)

U.A.T

Sign off

Stable Build

Defect Effected Build

Modified Build

Complete Build

Master Build

Golden Build




24 Manual Testing

MANUAL TESTING

Testing Process

Test Initiation(Project Management /

Quality Analyst

T.R.M(Test Responsibility

Matrix) 3) Risk involved in that Project2) Type of the Project1) Scope of the Project

Test Plan Document(Test Lead)

4) Whom to Test?

1) What to Test?

3) Who to Test?

Test Scenarios &Test Cases with

Step by stepprocedure

(Test Engineer /Tester

Test Case execution asBatches

Test Closer (Test Lead)Bug fixing

2) How to Test?

Re-testing &Regression Testing

UAT

Sign Off

Defect Report Final SummaryReport




Manual Testing 25

PETT Process (Process Expert Tolls and Techniques)

Requirement Gathering

Analysis

Test initiation Design

Coding Test Plan Document

Test Scenarios & Test Casewith Step by step process

Level ‘0’ Testing / Sanity Testing

Level ‘1’ Testing / ComprehensiveTesting / Batch Testing

Level ‘3’ Testing / Test Closure / PostmortemTesting / Pre-acceptance Testing

(1) Initial Build

(2) Stable Build

(5) Complete Build

(3) Defect EffectedBuildBug

Fixing

Level ‘2’ TestingRe-Testing / Regression

Testing

Defect Report(4) Modified

Build

User Acceptance Testing

Sign Off

(6) Master Build

(7) Golden Build




26 Manual Testing

Testing Initiation:

In general testing process start with “Test initiation”. In this, Project

Manager / Quality Analyst develop Test starting Document. This document

defines the required testing approach to be followed by the testing team.

During this document preparation they will concentrate on below (12)

components.

1) Scope & Objective. 7) Test Automation2) Budget Control. 8) Defect Tracing & Reporting3) Test approach. 9) Measurements & Matrix.4) Roles & Responsibilities 10) Change & Configuration Management

5)

Communication & Status Reporting 11) Risks & Mitigations6) Test deliverables 12) Training Plan.

1) Scope & Objective:The need of testing in the project.

2) Budget Control.Time & Cost allocation to the project.

Ex: As per U.S. Norms

3) Test approach

In this they will specify a list of selected quality factors to be

applied by the Tester.

T.R.M (Test Responsibility Matrix) can be finalized by Project

Manager / Quality Analyst based on scope of the project, type of the

project and Risks involved in that project.

TRM : It defines the mapping between Test factors and Development

Stages.

100%

64% DevelopmentDepartment

36% TestingDepartment

# ##




Manual Testing 27

Quality Factors / TestFactors

RG &Analysis Design Coding

Function &SystemTesting

R & M

1) Authorization

2) Access Control3) Ease of use4) Ease of operation5) Correctness6) Continuity &

Processing7) Coupling8) Data integrity9) Recovery

10) Portable11) Service Level12) Performance13) Maintainable14) Methodology15) Audit trail.1) Authorization: Whether a valid user is accessible or not and Invalid

User is preventable or not.2) Access control: Whether a valid user have permission to user specific

service of not3) Ease of Use: Whether the application build is providing user

friendly screens or not.4) Ease of operate: Easy to installation, downloading, uploading,

dumping, un-installing.5) Correctness: Whether the functionality output is right or wrong.6) Continuity & processing: The integration of modules.7) Coupling: Co-existence with other Software.8) Data Integrity: Whether the input objects are taking right type and

range of values or not.9) Recovery: Whether the application build is changing fromabnormal state to normal state or not.

10) Portable: Whether the application build is able to run ondifferent platforms or not.

11) Service Level: The order of functionality.12) Performance: The speed of processing.13) Maintainable: Whether the application build is longtime serviceable

in customers site or not.




28 Manual Testing

14) Methodology: Whether the people (Tester) are following right process of not. If not he will be punishable.

15) Audit Trail: Whether the system is maintains data for the user

operation (Ex. Bank Application, Withdrawal time,ATM Centre Code etc.,)

1) Authorization Security Testing2) Access Control Security Testing3) Ease of use User interface Testing4) Ease of operation Installation Testing5) Correctness Functionality Testing6) Continuity & Processing Integration Testing

7)

Coupling

Intersystem Testing8) Data integrity Input domain Testing9) Recovery Recovery Testing10) Portable Compatibility Testing11) Service Level Functionality Testing12) Performance Load, Stress, Storage, Data volume Testing13) Maintainable Stress Testing14) Methodology Compliance Testing15) Audit trail. Functionality Testing

4) Roles and Responsibilities Name of the jobs and his / her responsibilities.

5) Communication n& Status reportingThe required communication between two consecutive jobs.

Ex:

When do report? Weekly Once, twice, daily etc.,

6) Test deliverablesThe required documents to be prepared by the testing team. The

following documents were prepared by the Test lead and Test engineers.Test Plan, Test Scenario, Test Cases, Test Data, Test log, Defectreport, Final Summery Report etc.,

7) Test automationThe purpose of Automation testing in the project and available

tools in the organization.

Project Management Test Lead Test Engineer




Manual Testing 29

8) Defect tracing & Reporting.The required communication between Programmers and Testers

when Test Engineer / Tester got a mismatch.Large Scale Small Scale

Transmittal Report

9) Measurement & Matrix:The required measurement to estimate the status of the project. In

measurements there are (3) types such as (1) Quality AssessmentMeasurement (2) Test Management Measurement (3) Process CapabilityMeasurement.

10) Change & Configuration ManagementHow to handle change request from the customer and how to store

the documents for future reference.

11) Risk & Mitigations:The possible risks and solutions to overcome them.

12) Training Plan:The required training secession to the Testing team to understand

about the project.

Project Management

Project Lead

Team Lead

Programmer

Test Lead

Test Engineer

Project Management

Team Lead

Programmer

Test Lead

Test Engineer




30 Manual Testing

TEST PLAN

After completion of Test Strategy Document, the strategy of the Project

implemented by Test Lead in the Project through Test Plan.

During Test Plan Document preparation, Test Lead category people

follows below approach.

a) Team Formation:

In general Test Plan Document preparation starts with Team

formation. In this Test Lead category people form the Testing Team

depending on below factors.i. Project size.

ii. Project duration.iii. Availability of domain testers.iv. Resources (Automation Tools)

b) Identify Risks

After completion of Team Formation the Test Lead identifies risks

with respect to that formed testing team in Testing.i. Lack of time.ii. Lack of resources.iii. Lack of communication.iv. Lack of knowledge on project domain.v. Lack of test data.vi. Lack of development process rigor.vii. Delays in delivery.

BRS

TRM

Development Plan

a) Team formation

b) Identify risks

c) Prepare Test Plan

d) Review Test Plan

System Test Plan

Module Test Plan(if project is big then only ModuleTest Plan is to be prepared)




Manual Testing 31

c) Prepare Test PlanAfter completion of Team formation and Risk Analysis, Team

Lead will prepare Test Plan Document in IEEE (Institute of Electrical &Electronic Engineer) Format (829)

1) Test Plan ID 9) Exit Criteria2) Introduction 10) Test deliverables3) Test items 11) Test environment4) Features to be tested 12) Staff & Training needs5) Features not to be tested 13) Responsibilities6) Test approach 14) Schedule7) Entry criteria 15) Risks & Mitigations8) Suspension Criteria 16) Approved by

1) Test Plan ID:Unique number for feature reference.

2) IntroductionIntroduction about the project or module.

3) Test itemsThe name of the requirements or features.

4) Features to be testedThe name of the requirements or features to be test.

5) Features not to be testedThe name of the requirements or features not to be test

6) Test approachThe list of selected quality factors to be applied by the Tester.

7) Entry criteriaWhen to start Testing

Take complete and correct Test cases. Create Test Environment. Receive Stable Build from the developers.

8) Suspension criteriaWhen to suspend testing temporarily

When we have network problem. If pending defects are more

(Pending defects = No. of reported defects – No. of resolved defects)




32 Manual Testing

9) Exit criteriaWhen to stop testing

After completion of all module testing. After completion of all Major bugs resolved.

10) Test deliverablesThe required documents to be prepared by the Testers.

Ex.: Test Scenarios, Test Cases, Test Scripts, Test Data, Test log, DefectReport, FSR ………… etc.,

11) Test environmentThe required Software and Hardware to conduct Testing.

12) Staff and Training needsThe names of selected testers and their training needs.

13) ResponsibilitiesWork allocation to the testers.Ex. Modules Vs. Testers.

14) ScheduleTime duration to the testers.

15) Risks and MitigationsThe required solutions for the previously analyzed risks.

16) Approved byWho approved the document, the signature of the Project Manager.

Name of the Test Lead.

d) Review Test Plan:Completion of Test Plan Document preparation, Test Lead is conducting

Review Meeting to estimate completeness and correctness of that document.During this review they will concentrate on below coverages.

(i) Requirements Based Coverage (What to Test?)(ii) Risk Based Coverage (Who to Test & When to Test?)(iii) TRM Based Coverage (How to test?)




Manual Testing 33

T EST SCENARIOS & T EST C ASE DESIGN After completion of Test Plan Document and corresponding Reviews

Test Lad allocate the work to the Testers.Testers are preparing corresponding Test Scenarios and Test Caes based

on Requirement Specifications.USE C ASE Use Case is a required document which maintenance the detail

information about one low level requirement.If you want to design Test Cases based on Use Cases, we can study the

Use Case below approach.USE C ASE F ORMAT :TitleRequirement Description

Actors / UsersPre-operationActionPositive FlowsExceptions / Negative flowsAlternative flows / Alternative Positive flows

1) Collect all Use Cases.2) Take one Use Case and Study.

2.1) Identity Entry Point.

2.2) Identity Input Requirement2.3) Identity Outputs2.4) Identity Alternative flows and exceptions.2.5) Identity exit point.

3) Prepare scenarios.4) Review scenarios.5) Prepare Test Cass with step by step procedure.6) Continue from step (2) to (6) until completion of all Use Cases.

T EST SCENARIOS Test Scenarios means Test situations.

Test Scenario TemplateThese templates are created in MS Excel.

Project Name:Reviewed by

Module Name:Created by:

Reviewed byCreated on:

Sl. No. Requirement Name Test Scenario Test Cases




34 Manual Testing

T EST C ASES A set of Test steps documented along with required inputs and expected

results in order to test one low level requirement.

Thinks to remember while designing the Test Cases.1) Test Case should be simple and clear.2) Test Case should be complete.3) No duplicate Test Case should b written.

T EST C ASE T YPE 1) User Interface Test Cases.2) Usability Test Cases.3) Validation Test Cases.

4) Functional Test Cases.

1) User Interface Test CasesTo verify the look and Feel of application build screens.

Ex: Font Size, Text alignment, Images etc.,

2) Usability Test CasesTo verify ease of use of application build screens.

Ex:a) Default cursor should be present at the first field.

b) Tab keys should be implemented for all input objects from left to rightin downward direction.

c) Shortcut keys should be implemented for all menu operation.d) Tool tips (Whenever we place the cursor on particular object, it should

return meaningful message)

3) Validation Test Cases:Test Cases that are required to validate business rules or field

validation.

4) Functional Test Cases:Test Cases that are required to validate the functionality.

T EST DESIGN T ECHNIQUES They are mainly (5) types of design techniques.

(1) Boundary Value Analysis (BVA)(2) ECP (Equal Class Partition)(3) Error Guessing

(4) Decision Tables(5) State transition.




Manual Testing 35

(1) BVA:It is used to validate the range of input objects.

(2) ECP:

Splitting the inputs into equal parts and randomly checking them. To verify the type of input objects.

(3) Error GuessingIt is a technique which can be used by the people, who have prior

knowledge on that application (Ex. This can be used by experts)

(4) Decision TablesA Black Box Test Design testing in which test cases are designed

to execute the combination of inputs.

(5) State TransitionA Black Box Test design techniques, in which test cases are

designed to execute valid, invalid state transition.

Valid Invalid Valid Invalid

Valid Valid Invalid Valid

Insertcard

Wait for PIN Entry

1 st Entry

2nd Entry

3 rd Entry

BlockCard

AccessAccount

PIN Wrong

PIN Wrong

PIN Wrong

PIN Ok

PIN Ok

PIN Ok




36 Manual Testing

T EST C ASE T EMPLATE

Test CaseName / ID

Test CaseDescription Priority Step

NameStep

DescriptionTestData

1 2 3 4 5 6

ExpectedResults

ActualResults Status Created

ByCreated

on Comments

7 8 9 10 11 12

QC Path Reviewed

By

Reviewed

On

Reviewer’s

Comments13 14 15 16

1) Test Case Name / ID:Unique Number for future referenceEx: TC001_Project Name_Module Name_Functionality Name

2) Test Case Description:The description about that Test case.

Pre-requisites Documents referred.

3) PriorityImportance of the Test Case. They are classified into (3) Types

such as(1) High Priority (Basic functionality Test Cases)(2) Medium Priority (General functionality Test Cases – Recovery,Compatibility Testing etc.,)(3) Low Priority (Cosmetic Test Cases – User Interface Testing)

4) Step NameEvery Test Case divided into multiple steps, every step in the test

case will have unique number.Ex: Step–1; Step–2; Step–3 etc.,

5) Step DescriptionThe required action to be performed by the user.

6) Test DataSet of inputs that are required to execute steps.




Manual Testing 37

7) Expected ResultsThe required expected output from the system for the

corresponding user action.

8) Actual ResultsThe actual output of the system after performing user action.

9) StatusThe current position of the Test Case. They are classified into (4)

types, such as(a) No Run: Test Case not executed atleast for once.(b) Not complied: A partially executed test case.(c) Passed: Test Case executed and the expected value and

Actual value is same, “Test is passed”.(d) Failed: Test Case any step(s) expected valuesmismatched with actual value, “Test is failed”.

10) Created ByThe name of the Test Engineer, who created the Test Cases.

11) Created onDate and Time of the created Test Case.

12) CommentsA set of comments given by Tester for the Step or Test Cases.

13) QC PathThe path of Quality Control.

14) Reviewed By Name of the Reviewer.

15) Reviewed onWhen (Date & Time) the document was reviewed by reviewer.

16) Reviewer’s CommentsA set of comments given by reviewer.




38 Manual Testing

C ASE STUDY




Manual Testing 39

User NameUser Name object allows alphabets lower case range from 4 to 8

characters.

PasswordPassword object allows alphabets lower case range from 6 to 10characters.

Customer Name Customer Name object allows alphabets. Range from 4 to 12 characters. First letter should be Upper Case. Mandatory.

Customer Address Customer Address object allows alpha-numeric and some special

Characters (“–“ “/” “#” “,” “.”) Maximum of 20 Characters. Mandatory.

Customer DOB Customer DOB object allows Numeric Only. The format is MM/DD/YYYY. Date should be less than current system date. Mandatory.

Customer Ph.No. Customer Ph.No. object allows Numeric Only. Allows 10 digits only. Phone number is unique. Mandatory.

E–Mail E-Mail object allows alpha-numeric and special Characters. Format is [email protected]. It is not mandatory.




40 Manual Testing

T EST SCENARIO DOCUMENT

Project Name: Customer Info Reviewed by Module Name: Admin

Created by: Suresh Reviewed by Created on: 18/10/2008

Sl. No. RequirementName

TestScenario Test Cases

1 LoginOk

Cancel

1) Verify Ok with valid data.2) Verify Ok with invalid data.3) Verify Cancel

2 Add

Insert

Cancel

1) Verify Insert with valid data.2) Verify Insert with invalid

data.3) Verify Insert with duplicatedata.

4) Verify Insert with missingmandatory fields.

5) Verify Cancel

3 Search

Search

Cancel

1) Verify Search with validdata.

2) Verify Search with invalid

data.3) Verify Cancel

4 Edit

Update

CancelHome

1) Verify Update with validdata.

2) Verify Update with invaliddata.

3) Verify Update with duplicatedata.

4) Verify Update with missingmandatory fields.

5) Verify Cancel6) Verify Home

5 Delete Delete Verify Delete6 Cancel Cancel Verify Cancel7 Home Home Verify Home8 Logout Logout Verify Logout

Note: RCN (Requirement Clarification Note)Any doubt in FRS / BRS Document, we people design RCN Document and

the same will be sent to BDP for clarification.




Manual Testing 41

T EST C ASE DOCUMENT Test Case

nameTest Case

descriptionStep

NameStep

DescriptionTestData Expected Result

TC01_

Customer Info_Admin_ Verify Ok with Validdata

This Test

casevalidates‘Ok’functionalitywith validdata

Step-1 Open Brower,

enter Url.Address, click on Go

Url It should display Login

Page with User Name,Password objects and Ok,Cancel functionalities.

Step-2 Enter validUser Nameand Passwordclick on Ok

User Name& Password

It should displayCustomer Information

page with Add, Search,Logout functionalities.

TC02_ Customer

Info_Admin_ Verify Ok with invaliddata

This Testcase

validates‘Ok’functionalitywith invaliddata

Step-1 Open Brower,enter Url.

Address, click on Go

Url It should display LoginPage with User Name,

Password objects and Ok,Cancel functionalities.Step-2 Enter invalid

User Nameand Passwordclick on Ok

User Name& Password

It should displaymeaningful error message.

TC03_ Customer Info_Admin_ Verify Cancel

This TestcasevalidatesCancelfunctionality

Step-1 Open Brower,enter Url.Address, click on Go

Url It should display LoginPage with User Name,Password objects and Ok,Cancel functionalities.

Step-2 Enter User Name andPassword click on Cancel

User Name& Password

It should clear all fieldsand cursor should be

present in the first field.

TC04_ Customer Info_Admin_ Verify Insertwith Validdata

This Testcasevalidates‘Insert’functionalitywith validdata




User Name& Password



Step-3 Click on Add - - It should display AddCustomer page withC.Name, C.Addr.,C.DOB, C.Ph.No., E-mail objects and Insert,Reset, Cancelfunctionalities.




42 Manual Testing

Test Casename

Test Casedescription

StepName

StepDescription

TestData

Expected Result

Step-4 Enter data incorresponding

fields andclick on Reset

C.NameC.Addr.C.DOBC.PhNoE-mail



Step-5 Enter validdata incorrespondingfields andclick on Insert


It should display ameaningful Messagesuch as “Customer Datacreated with Customer ID”

TC05_ Customer

Info_Admin_ Verify Insertwith invaliddata

This Testcase

validates‘Insert’functionalitywith invaliddata




Password objects and Ok,Cancel functionalities.


User Name& Password



Step-3 Click on Add - - It should display AddCustomer page withC.Name, C.Addr.,

C.DOB, C.Ph.No., E-mail objects and Insert,Reset, Cancelfunctionalities.

Step-4 Enter invaliddata incorrespondingfields andclick on Insert


It should display ameaningful Error Message.

TC06_ Customer Info_Admin_ Verify Insertwithduplicate data

This Testcasevalidates‘Insert’functionalitywithduplicatedata




User Name& Password



Step-3 Click on Add - - It should display AddCustomer page withC.Name, C.Addr.,




Manual Testing 43

Test Casename


StepName

StepDescription

TestData

Expected Result

C.DOB, C.Ph.No., E-mail objects and Insert,

Reset, Cancelfunctionalities.Step-4 Enter

duplicate dataincorrespondingfields andclick on Insert



TC07_

Customer Info_Admin_ Verify Insertwith missingmandatoryfields

This Test

casevalidates‘Insert’functionalitywithmissingmandatoryfields

Step-1 Open Brower,





User Name& Password



Step-3 Click on Add - - It should display AddCustomer page withC.Name, C.Addr.,C.DOB, C.Ph.No., E-mail objects and Insert,Reset, Cancelfunctionalities.

Step-4 Enter data incorrespondingfields bymissing somemandatoryfields andclick on Insert




This Testcasevalidates‘Cancel’functionality




User Name& Password






44 Manual Testing

Test Casename


StepName

StepDescription

TestData

Expected Result

Step-3 Click on Add - - It should display AddCustomer page with

C.Name, C.Addr.,C.DOB, C.Ph.No., E-mail objects and Insert,Reset, Cancelfunctionalities.

Step-4 Enter data incorrespondingfields and click on Cancel


It should close current page and display previous page.

TC09_ Customer Info_Admin_ Verify Searchwith validdata

This Testcasevalidates‘Search’functionalitywith validdata




User Name& Password



Step-3 Click on

Search

- - It should display Search

Page with C.ID, C.Name,C.DOB, C.Ph.No.,objects and Search,Reset, Cancelfunctionalities.

Step-4 Enter data incorrespondingfields click onReset

C.IDC.NameC.DOBC.PhNo



Step-5 Enter validdata incorrespondingfields and click on Search


It should display SearchResults Page withCustomers Informationand Edit, Delete, Cancel,Home functionalities.

TC10_ Customer Info_Admin_ Verify Searchwith invaliddata

This Testcasevalidates‘Search’functionalitywith invalid



Step-2 Enter validUser Name

User Name





Manual Testing 45

Test Casename


StepName

StepDescription

TestData

Expected Result

data and Passwordclick on Ok

& Password


Step-3 Click onSearch

- - It should display SearchPage with C.ID, C.Name,C.DOB, C.Ph.No.,objects and Search,Reset, Cancelfunctionalities.

Step-4 Enter invaliddata incorrespondingfields and click on Search




This Testcasevalidates‘Cancel’functionality




User Name& Password





Step-4 Enter data incorrespondingfields and click

on Cancel


It should close current page and display previous page.

TC12_ Customer Info_Admin_ VerifyUpdate withvalid data

This Testcasevalidates‘Update’functionality




User Name& Password






46 Manual Testing

Test Casename


StepName

StepDescription

TestData

Expected Result


- - It should display SearchPage with C.ID, C.Name,

C.DOB, C.Ph.No.,objects and Search,Reset, Cancelfunctionalities.




Step-5 Select aCustomer data click onEdit

-It should display EditPage with C.ID, C.Name,C.Addr., C.DOB,C.Ph.No., E-mail objectsand Update, Reset,Cancel, Homefunctionalities.

Step-6 Enter data incorrespondingfields click onReset

C.IDC.NameC.DOB

C.Addr.C.PhNoE-mail



Step-7 Enter validdata incorrespondingfields click onupdate

C.IDC.NameC.DOBC.Addr.C.PhNoE-mail

It should display “Updatedone” message.

TC13_

Customer Info_Admin_ VerifyUpdate withinvalid data

This Test

casevalidates‘Update’functionalitywith invaliddata

Step-1 Open Brower,





User Name& Password




- - It should display SearchPage with C.ID, C.Name,C.DOB, C.Ph.No.,objects and Search,




Manual Testing 47

Test Casename


StepName

StepDescription

TestData

Expected Result

Reset, Cancelfunctionalities.





- It should display EditPage with C.ID, C.Name,C.Addr., C.DOB,C.Ph.No., E-mail objects

and Update, Reset,Cancel, Homefunctionalities.

Step-6 Enter invaliddata incorrespondingfields click onupdate



TC14_

Customer Info_Admin_ VerifyUpdate withduplicate data

This Test

casevalidates‘Update’functionalitywithduplicatedata

Step-1 Open Brower,





User Name& Password











48 Manual Testing

Test Casename


StepName

StepDescription

TestData

Expected Result

Step-5 Select aCustomer

data click onEdit

- It should display EditPage with C.ID, C.Name,

C.Addr., C.DOB,C.Ph.No., E-mail objectsand Update, Reset,Cancel, Homefunctionalities.

Step-6 Enter duplicate dataincorresponding

fields click onupdate

C.IDC.NameC.DOBC.Addr.C.PhNo

E-mail


TC15_ Customer Info_Admin_ VerifyUpdate withmissingmandatoryfields

This Testcasevalidates‘Update’functionalitywithmissingmandatoryfields




User Name& Password






C.IDC.NameC.DOB

C.PhNo



- It should display EditPage with C.ID, C.Name,C.Addr., C.DOB,C.Ph.No., E-mail objectsand Update, Reset,Cancel, Homefunctionalities.




Manual Testing 49

Test Casename


StepName

StepDescription

TestData

Expected Result

Step-6 Enter data incorresponding

fields bymissing somemandatoryfields andclick onupdate


It should displaymeaningful error

message.

TC16_ Customer Info_Admin_

Verify Cancel

This Testcasevalidates

Cancelfunctionality

Step-1 Open Brower,enter Url.Address, click

on Go

Url It should display LoginPage with User Name,Password objects and Ok,

Cancel functionalities.Step-2 Enter validUser Nameand Passwordclick on Ok

User Name& Password









- It should display EditPage with C.ID, C.Name,C.Addr., C.DOB,C.Ph.No., E-mail objectsand Update, Reset, Cancel,Home functionalities .

Step-6 Enter data incorrespondingfields andclick onCancel


It should close current page and displayPrevious Page.




50 Manual Testing

Test Casename


StepName

StepDescription

TestData

Expected Result

TC17_ Customer

Info_Admin_ Verify Home

This Testcase

validatesCancelfunctionality




Password objects and Ok,Cancel functionalities.


User Name& Password










- It should display EditPage with C.ID, C.Name,C.Addr., C.DOB,C.Ph.No., E-mail objectsand Update, Reset, Cancel,Home functionalities .

Step-6 Enter data incorrespondingfields andclick onHome

C.IDC.NameC.DOB

C.Addr.C.PhNoE-mail

It should close current page and displayCustomer Info Page.

TC18_ Customer Info_Admin_ Verify Delete

This TestcasevalidatesDeletefunctionality




User Name& Password






Manual Testing 51

Test Casename


StepName

StepDescription

TestData

Expected Result







Step-5 Select aCustomer data click onDelete

-It should removecustomer’s informationwith “CustomersInformation wassuccessfully deleted”.


This TestcasevalidatesCancelfunctionality




User Name& Password








Step-5 Select aCustomer data click onCancel

- It should close current page and display previous page.




52 Manual Testing

Test Casename


StepName

StepDescription

TestData

Expected Result

TC20_ Customer

Info_Admin_ Verify Home

This Testcase

validatesHomefunctionality




Password objects and Ok,Cancel functionalities.Step-2 Enter valid

User Nameand Passwordclick on Ok

User Name& Password




- - It should display SearchPage with C.ID, C.Name,C.DOB, C.Ph.No.,

objects and Search,Reset, Cancelfunctionalities.




Step-5 Select aCustomer data click onHome

- It should close current page and displayCustomer Info Page.

TC21_ Customer Info_Admin_ VerifyLogout

This TestcasevalidatesLogoutfunctionality




User Name& Password



Step-3 Click onLogout

- It should close current page and display LoginPage




Manual Testing 53

User NameUser Name object allows alphabets lower case range from 4 to 8

characters.

BVA & ECP for User NameBVA ECPRange Expected Actual Result Valid Invalid

Min= 4 Char Min-1= 3 Char Min+1= 5 Char Max= 8 Char Max-1= 7 Char Max+1= 9 Char


[a-z] [A-Z][0-9]All

Specialcharacters

PasswordPassword object allows alphabets lower case range from 6 to 10

characters.BVA & ECP for Password

BVA ECPRange Expected Actual Result Valid Invalid

Min= 6 Char Min-1= 5 Char Min+1= 7 Char Max= 10 Char Max-1= 9 Char Max+1= 11 Char


[a-z] [A-Z][0-9]All

Specialcharacters

Customer Name Customer Name object allows alphabets. Range from 4 to 12 characters. First letter should be Upper Case. Mandatory.

BVA & ECP for Customer NameBVA ECP

Range Expected Actual Result Valid InvalidMin= 4 Char Min-1= 3 Char Min+1= 5 Char Max= 12 Char Max-1= 11 Char Max+1= 13 Char


[a-z][A-Z]

[0-9]All

Specialcharacters




54 Manual Testing

Customer Address Customer Address object allows alpha-numeric and some special

Characters (“–“ “/” “#” “,” “.”)

Maximum of 20 Characters. Mandatory.BVA & ECP for Customer AddressBVA ECP

Range Expected Actual Result Valid InvalidMax= 20 Char Max-1= 19 Char Max+1= 21 Char

PassPassFail

[a-z][A-Z][0-9]

Some Spl.

Characters – / # , .

AllSpecial

charactersExcept

mentioned

Customer DOB

Customer DOB object allows Numeric Only. The format is MM/DD/YYYY. Date should be less than current system date. Mandatory.

BVA & ECP for Customer DOBBVA ECP

Range Expected Actual Result Valid InvalidMax= 20 Char Max-1= 19 Char Max+1= 21 Char

PassFailPass

[a-z][A-Z][0-9]

Some Spl.Characters

– / # , .

AllSpecial

charactersExcept

mentioned

Customer Ph.No. Customer Ph.No. object allows Numeric Only. Allows 10 digits only. Phone number is unique. Mandatory.

BVA & ECP for Customer Ph.No.BVA ECP

Range Expected Actual Result Valid InvalidMax= 10 DigitsMax-1= 19 DigitsMax+1= 21 Digits

PassFailPass

[0-9] [a-z][A-Z]

All Spl.Characters




Manual Testing 55

T EST DATA DOCUMENT Project Name

Reviewed byModule NameCreated By

Reviewed onCreated onSl.No.

Test CaseName

StepName

Datarequired Data generated Comments

1

TC01_ Customer Info_Admin_ Verify Ok withValid data

Step-1 Url http://192.168.1.0

/Customer Info 1.0

Step-

2

User Name

1) rama2) rames3) gahesha4) reliance

Password1) suresh2) sureshb3) sureshbug4) sureshbuga

2

TC02_ Customer Info_Admin_ Verify Ok withinvalid data

Step-1 Url http://192.168.1.0

/Customer Info 1.0

Step-2

User Name

1) ram2) sureshbug3) ga*1

4) ram@123

Password

1) sures2) sureshbugat3) SURESH4) sarvani@bu

3


Step-1 Url http://192.168.1.0

/Customer Info 1.0Step-2

U.Name pavaPassword ganesh

4

TC04_ Customer Info_Admin_ Verify Insertwith Valid data

Step-1 Url http://192.168.1.0/Customer Info 1.0Step-2


Step-5

C.Name

RamuSitaRamakrishnaKoteswararao

C.Addr. Koti,D.No.-5/G

Brundavancolony7/G-3




56 Manual Testing

Sl.No.

Test CaseName

StepName

Datarequired

Data generated Comments

C.DOB 05/25/1976C.Ph.No. 9440163282

E-mail [email protected]

5

TC05_ Customer Info_Admin_ Verify Insertwith invaliddata

Step-1 Url http://192.168.1.0

/Customer Info 1.0Step-2


Step-4

C.Name SaiSaisarvanibug

C.Addr.

Brundavancolony7/G*3

Brundavanacolony7/G-3C.DOB 25/10/1976C.Ph.No. +91-9440163282

E-mail suresh_240878#yahoo.com

6

TC06_

Customer Info_Admin_ Verify Insertwith duplicatedata

Step-1 Url http://192.168.1.0

/Customer Info 1.0Step-

2

U.Name pava

Password ganesh

Step-4

C.Name KoteswararaoC.Addr. Brundavancolony7/G-3C.DOB 05/25/1976C.Ph.No. 9440163282


7

TC07_ Customer Info_Admin_ Verify Insertwith missingmandatoryfields

Step-1 Url http://192.168.1.0

/Customer Info 1.0

Step-2 U.Name pavaPassword ganesh

Step-4



8

TC08_

Customer Info_Admin_

Step-1 Url

http://192.168.1.0/Customer Info 1.0




Manual Testing 57

Sl.No.

Test CaseName

StepName

Datarequired

Data generated Comments

Verify CancelStep-

2

U.Name pava

Password ganesh

Step-4



9

TC09_

Customer Info_Admin_ Verify Searchwith valid data

Step-1 Url http://192.168.1.0

/Customer Info 1.0

Step-2


Step-5

C.Name KoteswararaoC.DOB 05/25/1976C.Ph.No. 9440163282




58 Manual Testing

Review on Test CasesAfter completion of Test Case preparation, Test Engineer is conducting

Peer Review and Test Lead is conducting Lead Review to estimate“Completeness and Correctness” of that document

Peer Review

After completion of review on Test Cases, Test lead is mapping TestCases with Requirement Traceability Matrix Document. (RTM)

RTM defines the mapping between requirements and Test Cases.

Traceability Matrix TemplateProject Name Project Manager Prepared By Reviewed By

Prepared onReviewed onLast Updated on

Sl. No. RequirementDescription

Use CaseReference Test Scenario Test Case

Reference

T EST C ASE E XECUTION

After completion of Test Cases preparation and corresponding reviews,Testers are receiving initial build from the development people.

During Test Case execution Testers are receiving modified build from thedevelopers. To receive any type of build from the developers, Testers requireda valid negotiation / communications with developers like as below.

PM PL

TE-1 TE-2




Manual Testing 59

E XECUTION L EVELS :

COMMON REPOSITORY / SOFT BASE

VSS (Visual Source Safe)The versions have been maintained

by these VSS

1.0 2.0 3.0

FTP (File Transfer Protocol)

Deploy / Install BuildSanity Testing

Testers

Developers

Client

Initial Build

Level ‘0’Sanity Testing

Level ‘1’Comprehensive

Testing Bug Fixing

Level ‘2’Re-Testing

Regression TestingLevel ‘3’

Test Closer Test Lead

U.A.T

Sign off

Stable Build

Defect Effected Build

Modified Build

Complete Build

Master Build

Golden Build




60 Manual Testing

T EST H ARNESS :Test Harness means ready to start testing.Test Harness = Test Environment + List of Test Cases.

L EVEL ‘0’ T ESTING After receiving initial build from the development people, Testers areconducting Level ‘0’ Testing to estimate stability of that build before start realtesting.

In this testing, Testers are concentrates on Core (Basic) functionalities.During this Testing they will concentrates on below factors.

1) Under standable.2) Operatable3) Observable

4) Controllable.5) Consistency.

6) Automatable.7) Maintainable.8) Simplicity.From the above factors Level ‘0’ Testing is also known as “Oct-Angle

Testing” or Sanity Testing or Build Verification Testing or Tester AcceptanceTesting or Testability Testing.

L EVEL ‘1’ T ESTING It is also known as “Comprehensive Testing”. During this testing Testers

are executing all P 0, P 1, P 2, Test Cases (P 0 –High Priority, P 1 –Medium Priority,P2 –Low Priority) to validate functionality. In this every Test Case has to beexecuted by Tester either in Manual or in Automation.

Build

Test Engineer

Test Cases

Build

AutomationTesting

Test Cases

Test Engineer Manual Testing

Automation Testing




Manual Testing 61

Execution Process

Defect Report

During test execution, Testers are reporting mis-matches to developmentTeas as “Defect” in Defect Report Document.

Defect Report Format1) Defect ID

Unique for future reference.

2) SummaryBrief description of the defect.

3) FeaturesThe name of the feature / functionality in which defect.

4) Test Case Name Name of the Test Case (in which Test Case execution the defect is

raised)

5) ReproducibleThe defect is repeatable in every time execution.

a. If Yes: It is reproducible, attach test procedure. b. If No: It is not reproducible, attach test procedure along with snap

shots.

6) StatusStatus of the defect. They are (2) types(i) New–Reporting for first time.(ii) Re-open–For re-reporting defects.

Take all the TestCases

Test CaseExecution

Blocked Test Cases

Close

Partial Pass or Fail

Skip

Fail

Pass




62 Manual Testing

7) Severity (Seriousness with respect to Testers) It means seriousness of the defect with respect to Tester or

seriousness of the functionality. They are classified into (3) Types suchas

(i) High severity – Urgent to solve(ii) Medium severity – Mandatory to solve(iii) Low severity – Compulsory to solve

8) PriorityImportance of the defect with respect to customer or importance of

the functionality. It is classified into (3) types such as(i) High Priority

(ii)

Medium Priority(iii) Low Priority

9) Assigned to Name of the Developer

10) Detected By Name of the Tester (Who detected the defect)

11) Reported onDate and Time

12) Build Version IDIn which version of the build the defect is raised.

13) Suggested to fixSuggestions to developer to fix the defects

By Developers

Fixed By: Name of the Programmer who fixed the defect.

Resolved onDate and Time

Resolution Type:Acknowledgment from the developers for the reported

defect.

Approved bySignature of the Team Lead / Project Lead.




Manual Testing 63

Types of defects1) User interface defects ( Low Severity)

Spelling mistakes (High Priority)Improper alignment (Low Priority)

2) Input domain defect (Medium Severity)Input type is not taking valid type ((High Priority)Input type is taking invalid type also (Low Priority)

3) Error handling defect (Medium Severity) No error message for wrong operation (High Priority)Complex message in error message (Low Priority)

4) Calculation defect(High Severity)Wrong outputs (High Priority)

5) Load conditional defect (High Severity) Build is not supporting more than one user (High Priority)Build is not supporting customer expected load (Low/Medium Priority)

6) Hardware defect (High Severity)Build is not supporting any hardware devices (High Priority)Build is supporting hardware and wrong output coming from hardware(Low Priority)

7) Role conditional defect (High Severity )System crash, Showstoppers, Dead lock etc.,

8) Version control system (High Severity) Mistake in version control

9) Source defects (Medium Severity) Mistake in Help Document (High Priority)

What is defect Age?The time gap between defect reported on and defect resolved on.

What is Build Internal period?The time gap between two consequent builds is called as Build Internal

period.




Manual Testing 65

Case 1: If the development team resolved bug severity is high, then Testersare re-executing all P 0, P 1, P 2 Test Cases on that modified build.

Case 2: If the development team resolved bug severity is medium then,Testers are re-executing all P 0, some P 1 and selected P 2 Tests cases

on that modified Build.Case 3: If the development team resolved bug severity is low, then Testersare re-executing some P 0 and selected P 1 and P 2 Test cases on thatmodified build.

Case 4: If the development team released modified build due to somechange request then the Testers are re-executing all P 0, P 1, P 2 TestCases on that modified build.

L EVEL ‘3’ T ESTING

After completion of all test cases execution and corresponding bugsresolving, Testers are sending complete build to the Test lead along with FSR (Final Summary Report)

After receiving Final Summary Report from the Testers, Test lead isconducting “Test Closure” to estimate that whether the Test Engineer meets exitcriteria or not.

In this Test lead category people will concentrate on below coverages.1) Requirements Coverage:

All the requirements with respect to functionality.

2) Bug density No. of defects in Module . No of defects in the Project

3) Analysis of deferred bugs:Whether the deferred bugs are reasonable or not to postpone.

After completion of above like coverages Test lead is conducting TestClosure in below approach.

Take High Bug density Module

Effort Estimation

Plan Regression

Do Regression

Do Regression

Do Regression

X 100




User Acceptance TestingAfter completion of “Test Closure” the Project Manager collects

feedback from the customers on developed software through “User AcceptanceTesting”. They are two types such as

α – Test(Alfa Test)

β – Test(Beta Test)

Software Application.By Real customer.At development site.

Software Product.By Model customer.At customer site.

Signoff After completion of User Acceptance Testing and corresponding

modifications, the Project Management deliver that software / build to the clientalong with Software Delivery Note (S/w DN). It consists of (2) issues such as

(i) User Manual.(ii) Known issues