Complete Guide to Manual Testing@Kumar

8/13/2019 Complete Guide to Manual Testing@Kumar

1/50

MANUAL TESTING

5) Q. Why explicitly the testing engineers are been recruited into the softwarecompanies?

Ans: 1) One person cant perform two task efficiently at a time.

2) Sentimental Attachment.

ro!ect:"

Project is something that is developed based on the partic lar c stomersre! irements and sed by that partic lar c stomers only.

roduct:"

Prod ct is something that is developed base on the companies specificationand sed by the m ltiple c stomers.

#$%&:" "he company will decide the specification by picking the common re! irements ofc stomer.

') Q. (lassical definition of uality ?

Ans : Quality is defined has j stification of all the re! irements of a c stomer in a prod ct.

#$%&: Quality is not defined in the prod ct it is defined in the c stomer mind.

*efect: #efect is defined as de+iation from the re! irements.

,) Q. -atest definition of uality?

Ans$ % ality is defined as not only the j stification of the re! irements b t also presence of

the val e & +alue ..means .. user friendly '

) Q. What is testing?

Ans$ "esting is a process in the defects are /dentified0/solated &separately'( ub!ect for 2ectification &sending' ns re that the prod ctis defect free in order to prod ce a ! ality prod ct in the end and hencec stomer satisfaction.

3)Q. What is bidding the pro!ect?

1


2/50

Ans$ *idding the project is defined as re! est are proposal( estimation and signingoff+official,agreement).

4/(4 $ 6&&%/#7 :" -ick off meeting is the initial meeting cond cted inthe software company soon after the project is signed off in order disc ss theo+er+iew of the pro!ect once select pro!ect manager for that project.

s ally

/igh level management &/01'

Project managers &P1'

% ality managers &%1'

"echnical managers &"1' #evelopment leads "est leads

3ill be involved in this meeting Apart from them many times c stomer representations also

3ill be involved in this meeting.

#$%&:" Apart from this meeting any other start p meeting in also called as 4 8ic8 offmeeting 5.

/# 9 ro!ect /nitiation #ote :" /# 6t is a mail prepared by the projectmanager and sent the 7 O of software company as well as to all of his core team members in order to intimate then that they are abo t to start the act al

project activities.

7 O87hief 9ec tive Officer

7OO87hief Of Officer

*-( 9 oftware *e+elopment -ife (ycle :"

6t contains ' Phase

6nitial or :e! irement Phase

Analysis Phase

#esigned Phase

7oding Phase +or) Programming phase

2


3/50

"esting Phase

#eliver and maintenance Phase

/nitial or 2e uirement hase:"

%as8:" 6nteracting with the c stomer and gathering the re! irements.

2oles:" i) * siness Analyst &*A'

ii) ngagement manager & 1'

rocess:" ;irst of all the * siness Analyst can Appointment . from the c stomer( collectsthe template from the company meet the c stomer an the appointment date gathers there! irements with the help of the template and come back to the company with there! irement doc mentary.

"he ngagement manager will go thro gh the re! irements doc ment. 6f at all hefinds any e9tra re! irements hence he will deal with the e9cess cast of project. 6f it is anyconfession of re! irements then the will ask the cons lt team to develop the prototype hewill demonstrates to the c stomer gather the clean re! irements and finally hand over there! irements doc ment to the b siness analyst.

roof:" Proof of this phase is 4 2e uirements *ocument; .

"his doc ment is called with different name in different companies ;:S +; nctional :e! irements Specification)

7:S +7lient or 7 stomer :e! irements Specification)

:S + ser :e! irements Specification)

*## +* siness #esign #oc ment)

*# +* siness #oc ment)

*:S +* siness :e! irement Specification)

#$%&:" Some companies may maintains two doc ments in the initial phase( one is for


4/50

rototype:" Prototype is a roughly and rapidly developed model which issed is for demonstration to the c stomer in order to gather the clearre! irement and also to win his confidence of the c stomer.

Analysis phase:"

%as8:"

;easibility st dy

"entative planning

"echnology selection nvironment conformation

:e! irement analysis

2oles:"

System Analyst &SA'

Project 1anager &P1'

"eam "echnical 1anager &"1'

rocess:"

easibility study:" =possibility) 6t is a detailed st dy cond cted on re! irement in order toconform whether all of those re! irements are possible with in the given time b dget andreso rces are not.

%entati+e planning =%emporary): , "he reso rce planning as well as sched ling will betemporary planned section.

%echnology selection > &n+ironment conformation:" "he list of all the technologies thatare re! ired to accomplish this project s ccessf lly will be enlisted as well as the clientenvironment will be conformed here in this section.

2e uirement analysis:" "he list of all the re! irements that are re! ired by the companylike h man reso rce ( software and hardware to accomplish that project (s ccessf l will beenlisted and mentioned here in this section.

roof: "he proof doc ment if the analysis phase is 2 = ystem 2e uirementpecification )

*esigned hase:"

%as8:" i ) /igh 0evel #esigning &/0#'

ii) 0ow 0evel #esigning &00#'

4


5/50

2oles:" i) 7hief architect +7A) $ is responsible for high level designing.

ii) "echnical 0ead +"A)$ is responsible for low level designing.

rocess:" "he chief architect will divided whole project into mod les (by drawing some

diagrams sing a lang age 6-= nified 1odeling 0ang age )

"he technical lead will divided the mod les into s b mod les by drawing somediagrams sing the same 6-.

Apart from this takes 7 / design also will be done in this phase.

Some time pseudo code also will be developed in this phase.

roof:" "he proof doc ment of this phase is %** +%echnical *esign *ocument )

seudo code:" 6t is set of nglish statement which sed for developing in theact al code very easily and comfortably.

(oding hase:"

%as8:" coding +or) programming

2oles:" #evelopers +or) programming

rocess:" "he developers will develop the act al so rce code with the s pport of technicaldesign doc ment as well as by following the coding standards.

&xample for coding standards:

Proper indentation

7olor coding.

Proper commenting.

roof:" "he proof doc ment of the coding phase (* = ource (ode *ocument).

%esting phase:"

%as8:" "esting

2oles:" "est engineers

rocess:"

5


6/50

"est engineers will receive the re! irement doc ment and will startnderstanding the re! irement.

3hile nderstanding the re! irement if at all the get any do bt then they willlist o t all the do bt in the re uirements clarification note and will send it tothe a thor of the re! irement do bt @A=* siness Analyst ).

Once the clarification are given if still more clarification are re! ired then theywill cond ct a re+iew meeting and will get all the clarification.

Once all the re! irement are clearly nderstood then they will take the %estcase template and will write the test cases.

Once the 1st * ild is released they will e9ec te the test cases.

6f at all any defects are fo nd they will list o t then in the defect profile andwill send it to the development department .

Once the ne9t * ild is released they will re e9ec te the re! ired test case.

6f at all any more defect are fo nd they will pdate the defect profile and willsend it to the development department.

Once the ne9t * ild is released the same process will be contin ed.

"his process will be contin ed again and again till the prod ct is defect free .

roof:" "he proof the testing phase is Quality roduct .

%est (ase:" 6f is an 6dea of test engineer to test something based on there! irements.

*eli+ery > 6aintains hase:"

*eli+ery:"

%as8:" /and overring the application to the client .

2oles:" #eployment ngineers or 6nstallation ngineers

rocess:" #eployment engineers will go to the clients place ( install the application into theoriginal c stomer ( nvironment and finally hand overs the software to the c stomer.

roof:" "he final official argument made between the company and the c stomer is the proof doc ment this phase.

6


7/50

6aintains:" Once the c stomer start sing the application if at all any problem occ rs thenthat problem will become the task (based on the task corresponding roles will be appointed(these roles will define the process( solves the problem and final get the Application latter .

Some c stomer many re! est for contin os maintenance in that sit ation thecompany will send a team of member to the c stomer place contin o sly in order to take careof that software .

Q. where exactly testing comes in to picture?

Which sort of testing you are expecting?


8/50

7ray @ox testing:" 6t is a method of testing in which one will perform testing on both thef nctional part as well as the str ct ral part of an application.

s ally the test engineers who have the knowledge of str ct ral part will perform it.

-e+els of %esting :"

"here are fi+e le+els of testing

nit level testing.

1od le level testing.

6ntegration level testing.

System level testing.

ser acceptance level testing.

nit le+el testing:"

nit:" nit is defined as smallest part of an application.+program)

6n this stage the white box testing will test each and every developed programand also the combination of programs.

6odule le+el testing $,

6odule:" 1od le is defined as a group of related features to perform a ma!or tas8 in theapplication.

6n this stage the @lac8 box test engineers will test the f nctional part of themod le.

/ntegration le+el testing:" 6n this stage the developers of will develop someinterface= linking program ) in order to integrate the mod les this interface will be tested bywhite bo9 testers. #evelopers will follow any one of the approaches white integration the

mod le.

"op down approaches

*ottom p approaches

/ybrid approaches +or) Sand rive approached

*ig,*ang approaches

%op down approaches:" 6n this approaches the parent mod les will be

developed first and then the corresponding child mod les will be developedand integrated.

8


9/50

% @:" 3hile integrating the mod les in top down approach if at all any mandatorymodules are missing then that mandatory mod les will be replace with a temporaryprogram.

@ottom up approach:" 6n this approached the child mod les will bedeveloped first and will be integrated to the corresponding parent mod les.

9


10/50

*2/ &2:" 3hile integrating the mod le in bottom p approached if at all any mandatorymodules is missing then that mod les is replaced with a temporary program 4#:6> :5


11/50

6n this stage the block bo9 test engineers will cond ct many type of testing likeload testing( performance testing( stress testing( comparability testing( system integrationtesting??..ect.

ystem integration testing:" 6t is a type of testing in which on will performsome action on mod le and check for the reflections in all the related are as ofthe application.

ser acceptance le+el testing:" 6n this stage the block bo9 test engineer will perform testingon the ser desired areas in the presence of accept the application happy .

&n+ironment:"

nvironment defined as gro p of hardware compo nds with some basicsoftware +$ ) where one can install the resentation -ogic0 @usiness -ogic0 *ata @ase

-ogic.

&or'

nvironment defends as combinations of three layer that is resentation-ayer0 @usiness -ayer0 *ata @ase -ayer. 3here once can install the resentation -ogic0@usiness -ogic0 *ata @ase -ogic.

%ype $f &n+ironment:"

Stand Alone nvironment +or) One "ier Architect re.

7lient Sever nvironment +or) "wo "ier Architect re.

3eb *ased nvironment +or) "hree "ier Architect re.

#istrib ted nvironment +or) @,"ier Architect re.

tand Alone &n+ironment =or) $ne %ier Architecture:"

6n this environment only one tier will be there. Presentation layer( b siness layer(data base layer will be present in the same tier.

3hen ever the application need to be sed by single ser at timethen environment will be s ggested.

11


12/50

(lient e+er &n+ironment =or) %wo %ier Architecture:" 6n this environment two tier will be there .one is for client and another is for data base server. Presentation layer and the b siness layer will be available is each and every client and the data base player will be present in data base server.

3hen ever the application need be sed single premises and there is no problem with the sec rity of the. * siness logic as well as the application need accessed veryfast lye then this environment be s ggested.

Web @ased &n+ironment =or) %hree %ier Architecture:" 6n this environment three tier will be there one is for clients( the middle is one is for application sever and the other is for data

12


13/50

base sever. presentation layer available in the client b siness layer will be available in theapplication server. data base sever.

3hen ever the application need to be sed all over the world by limitedn mbers of ser and wo nds the b siness logic will be sec red and f nction pdaters to beeasily them the in environment can be s ggested.

W&@ &2 &2 $, 3eb server is a software which provides web services tothe client.

&B$, 66S+6nternet 6nformation Services)

*istributed &n+ironment =or) #"%ier Architecture:" "his environment is same as webenvironment more the one application sever is introd ced in separate hers in order todistrib ted the load and increase the performance.

3hen ever the application needs to be se by h ge n mber of ser then thisenvironment can be s ggested.

13


14/50

%


15/50

UNIT TEST

INT TEST

MOD TEST

SYS TEST

UAT

Ad+antages $, 6t is a simple model and easy to implement.

Project 1onterey and maintains is very easily.

*raw @ac8:" 7ant accept the new re! irements in the middle of the process.

rototype 6odel:"

15

UN CLEARREQ

#ROTOTY#E

S!"#ROTOTY#E

!" #ROTOTY#E DEMO TOCLIENT

DEMO TO CLIENT

REQ ARERE'INED

BRS DOC BASE

CLIENT

ENVIRONMENTCON'ORMATION

SRS DOC BASED

LINED


16/50

Ad+antage:" when ever the c stomer is not clear with his re! irement. "hem this is bests itable model

*raw @ac8:" 6s not a compiled develop process model.

6ts a still time cons mer model.

7ompany sho ld where the cost of prototype

ser may limit re! irement by sticking into the project.

&+olutionary 6odel:"

16

INITIALREQ

DEVELO#

A##LICATION

USERVALEDATION

'EED BAC$"IT NE" REQ

USERACCE#T

NO

YES


17/50

A##LICATION

BASELINE

Ad+antage:" when ever the c stomer is evol tion the re! irement then this is the *ests itable model

*raw @ac8:" time cons ming model

7ostly model

#eed lines cant properly define.

@o transference.

Project monetary any maintenance is very diffic lt.

piral 6odel:"

1( DEINING T E OB)ECTVES !"OR$ ANALYSIS!CONSTRAINTS

4(RE'INIG &

#LANNING 2( RIS$ ROOT

'OR T E NE%T CYLE CAUSE

ANALYSIS

ESTIMATION

17


18/50

3( IM#LEMENATIONCONTINGENCIES

Ad+antage:" 3hen ever the project highly risk based then this is the best s itable model.

*raw @ac8:" "ime cons ming model.

7ostly model.

:isk root ca se analysis is nota easy task.

ish 6odel:"

REQ ANAYSIS DESIGN CODINGDELIVERY MAI*GAT ERING

SYSTEM T+ -./ 1aintan

SRS LD SCD

BRS REVIE" LLDBLOC$ B T+ -./

T+ - S!"

SRS REVIE" TDD REVIE" " IT BO% TESTINGC / +

Ad+antage:" As both the verification are done the o tcome will be a ! ality prod ct.

18


19/50

*raw @ac8:" "ime cons ming.

7ostly model.

"6odel:"

>erification >alidation

INITIAL & BRS#RE#ARING #RO)ECT #LANNINGANALYIS SRS#RE#ARING TEST #LANNING

DESIGN & TDDDESIGN # ASE TESTING CODING SCD

#ROGRAM # ASE TESTING

TESTING S!" BUILD SYSTEM TESTING TESTMANAGEMT #ROCESS USER ACCE#TANCE TESTING

DEVIVER & #ORT TESTINGMANINTENANCE S!"E''ICIENCY DRE A TEST S!"C ANGS A B

A D+ + - /: ;< - + -+ -./ -+ =B D+ + - > . +: ;< - + - =+>Ad+antage:" As both the verification and validation is done and test management process ismaintained. "he o tcome will be ! ality prod ct.*raw @ac8:" 6t is time cons ming model. 6t is a costly model.

erification:" >erification is a process of checking whether the prod ct is beingdeveloping in a right manner or not.

alidation:" >alidation is a process of checking whether the develop prod ct is rightor not.

%C & $ %& %/#7:"

19


20/50

* ild acceptance testing +or) * ild verification testing +or) Sanitytesting

:egression testing

:e testing

/alf, testing

*,testing

Static testing

#ynamic testing

6nstillation testing 7ompatibility testing

9ploratory testing

nd,"o, nd "esting

Sec rity testing

sability testing

:eliability testing

1 tation testing

Adhoc testing

@uild acceptance testing =or) @uild +erification testing =or) anity testing:"

6t is a type of testing in which one will cond ct overall testing one the released b ild inorder to conform where the proper of not for cond cting detailed testing

6n this type of testing s ally they check the following.

20


21/50

i) 3eather the b ild can be properly installed in to environment or not

ii) 3eather one can navigate to all the pages of the application or not.

iii) 3eather all the important feat re are available or not.

iv) 3eather all the re! irement connections are properly established or not.

6n some company they will call this types of testing as mo8e testing also b t in some companies they say that j st before releasing the b ild the developer will checkweather the b ild is proper or not i.e. know as mo8e testing.

Once the b ild is released the testing engineers will once again check weatherthe b ild is proper or not i.e. knows as *A" +or) *>" +or) sanity testing.

2egression testing:" 6t is a type of testing in which one will perform testing on the readytesting f nctionality again and again s allay it is done in two servicers.

i) 3hen even some defects are identified raised to the development department oncethe ne9t b ild is released the testing engineers will check the defect f nctionality aswell as the related f nctionality once again.

ii) 3hen ever some new feat re are added i.e. the application ne9t b ild is released tothe testing department then the test engineers will check all the related feat res ofthose new feat res once again.

#$%&: " "esting new feat res for the first time not regression testing.

Some companies may do 2andom testing at the end that also will fall nderregression testing only.

2etesting: " 6t is a type of testing in which one will perform testing on the same f nctionalityagain and again with m ltiple sets of data in order come to a concl sion weather thef nctionality is working fine or not.

#$%&:"

i) :egression testing starts form the Dnd b ild and contin e p to the last b ild.

ii) :e testing starts from the 1 st b ild and contin o s p to the last b ild.

iii) # ring regression testing also re testing will be cond cted that is the reasonsome people even call it as 2e and 2egression testing.

21


22/50


23/50

3ith draw ,,,,,,,D(CCC

*alance stmt ,,,,,,,,,,E(CCC

0ogo t

ecurity testing $, 6t is type of testing in which one will perform testing on the application inorder to conform whether it is properly protected +or)not.

i) Authentication testing : 6t is a type of sec rity testing in which one will enterdifferent combination of ser names and password .and check whether onlya thori


24/50

vi) : PO:"

%est planning:" "est plan is strategic doc ment which contains some information thatdescribes how to perform testing on that application in a effective (efficient and optimi


25/50

I.C) "est environment

E.C) :eso rces planning

J.C) Sched ling

K.C) Staffing and training

BC.C) :isk and consistencies

BB.C) Ass mption

B2.C) Approval information

1.F) /#%2$* (%/$#:"

$b!ecti+e: " P rpose of the doc ment will be clearly described here in thissection.

2eference document: , "he list of the doc ment that are referred will preparing this doc ments will be listed o t here in this section

&B: , S:S( Project plan

D.F) ($ &2A7& %& %/#7: ,

eatures are tested: " "he list of all the feat res with in the scope which are

to be tested will be listed o t here in this section. eatures not be tested:" "he list of all the feat res that are not planed for

testing will be listed o t here in this section.

&B:" i) O t of scope feat res

ii) 0ow risk feat res

iii) ;eat res that are planed to be incorporated in feat re

iv) ;eat res that are skipped based on the time constrains.

G.F) %& % %2A%&7&:" = defines )

"est strategic is an organiEation level term which is common for all the project in that organi


26/50

%ype of testing: " "he list of all the type of testing that all perform in that companywill be listed o t here in this section.

%est design techni ues: " "he list of all the techni! es that sed in that companywhile designing test cases will be listed o t here in this section.

&B: , *>A( 7P

(onfiguration management:"

%est 6etrics: " "he list of all the metrics that are maintained on the company doingthe test process will be listed o t here in this section.

&x: " #efect 1etric

"est case 1etric

%erminology: " "he list of all the terms sed in that company along with theirmeaning will be listed o t here in this section.

Automation plan: " "he list of all the areas that are planned for a tomation in thatcompany will be listed o t here in this section.

-ist of automated tools: " "he list of all the a tomated tools that are sed in thatcompany will be listed o t here in this section.

H.C) @ase criteria:"

Acceptance criteria: " 3hen to stop testing will be clearly described in this section.

uspense criteria: " 3hen to s spense testing will be clearly described here in thissection.

5.F) %est deli+erables: " "he list of all the doc ment that are to be developed of deliverydoing testing process testing process will be mentioned here on this section.

I.C) %est en+ironment $,"he details of environment that is abo t to be sed for testing will beclearly mentioned here in this section.

26


27/50

E.C) 2esource planning:" 3ho has to do what will be clearly described here in this section.

J.C) cheduling =or) %ime planning:" "he starting dates and ending dates of each and evertask will be clearly planed and mention in this section.

K.C)taffing and training:" "o accomplish that project s es f lly if at all any staffre! irement and if at all any training re! irement then that detailed will be clearly mentionhere in this section.

BC.C) 2is8 and (ontinence $, "his list of all the potential risk and continence sol tion planwill be clearly mentioned here in this section.

9$, mployee may leave the company the middle of the projectL

Ans . mployee need to mint on benched.

nable to de clearly project with in the deadline projectL

Ans. Proper plan ins rance.

7ost mer may impose the deadlineL

Ans. 3hat not be tested sho ld planned.

nable to test all the feat re with in the given timeL

Ans. Priority based the e9ec tion.

BB.C) Assumptions: " "he listed of all the think that are be ass med by the test engineer will be clearly mentioned here in this section.

B2.C) Approached information:" 3ho has approval this doc ment when it is approval will be clearly described in this section.

ii)%est de+elopment phase:"2e uirement *ocumentation

- & (A &

27

HLI

L L I

SCREEN

SHORT


28/50

se cases:" se case describes of the f nctionality of certain application terms ofaction response.

-ogin

i) unctional re uirement

ii) pecial re uirement

unctional re uirement:"

0ogin screen sho ld contain ser name( password connect to fields login( clear( cancel b tton.

7onnect fields is not mandatory b t it sho ld be allow ser to select the data base optionwhen ever re! ire.

pon entering valid ser name( password and clicking on login b tton correspondingpage m st be displayed.

pon entering in to any of the fields and clicking on clearly b tton all the fields m st becleared and co rser sho ld he display in the ser name.

pon clicking on cancel b tton login screen m st be closed.

pecial re uirement:"

6nitial when ever the login page invoked login and when ever and clear b tton isdisabled.

7ancel b tton m st be all ways enable.

pon entering some information in to and of the fields clear b tton m st be enabling.

pon entering some information in to both ser name and password fields login b tton m st be enabling.

"abbing order m st be ser name( password( connect to( login( clearer( cancel.

28

ser #ame

assword

-ogin (lear (ancel


29/50

se case template:"

i) @ame of the se case

ii) *rief description of the se case

iii) Action in val ed

iv) Special re! irement

v) Pre condition

vi) post condition

>ii);low condition

se (ase *ocument $,

#ame of the use case:"

i) @ame of the se case$ 0ogin se case

ii) *rief description the se case$ "his se case describes the f nctionality of all thefeat res present in the login screen.

iii) Actors involved$ #ormal user and Add mine user.

i+) Special re! irement$ two types

9plicitly re! irement

6mplicitly re! irement

&xplicitly re uirement:" "he re! irement the e9plicitly given by the c stomer are knowas e9plicitly re! irement.

/mplicitly re uirement: "he re! irement that are analy


30/50

Open entering invalid ser name valid password and click on login b tton the followingerror message m st be displayed. 46nvalid ser name please try again5.

pon entering valid ser name in valid password and click on login b tton following errormessage m st be displayed. 5invalid password please try again5

pon entering invalid ser name invalid password and click on login b tton following errormessage m st be displayed. 5invalid ser name and password please try again5

6nitial when ever the login screen is invoked the c rser m st be display on the ser namefields.

recondition:" login screen m st available.

ost condition:" ither home page +or) add mine and error message for invalid ser .

low of e+ents:" "wo typesi) 1ain flow

ii) Alternative flow

6ain flow:"

Action

Actors invoke the application.

Actors entrees valid ser name valid password and click on login b tton.

Actors entrees valid ser name valid password select a data base also and click on login b tton.

Actors entrees invalid ser name valid password and click on login b tton.

Actors entrees invalid password valid ser name and click on login b tton.

Actors entrees invalid ser name invalid password and click on login b tton.

Actors entrees some information into any of the field and click on clear b tton.

Actors click on cancel b tton.

30


31/50

2esponse

Application display the login screen with the following fields ser name( password( connectto( login( clear( cancel.

A thentication( application display either home page +or)admin page depending pon theactor entered.

A thentication( application display either home page +or)admin page depending pon the

actor entered with the mentioned data base connections .

=o to Alternati+e flow %able 1 +6nvalid ser name)

=o to Alternati+e flow %able D +invalid password)

=o to Alternati+e flow %able G +invalid ser name and password).

=o to Alternati+e flow %able H +clear click).

=o to Alternati+e flow %able 5 +cancel click).

31


32/50

Alternati+e flow %able 1:"

Action

Actors enters invalid ser name valid password and click on login b tton.

Alternati+e flow %able D:"

Actors enters in valid password valid ser name and click on login b tton.

Alternati+e flow %able G:"

Actors enters invalid ser name invalid password and click on login b tton.

Alternati+e flow %able H:"

Actors enter some information into any of the fields and click on clear b tton.

Alternati+e flow %able 1:"

Actors click on the cancel b tton.

32


33/50

2esponse

A thentication( Application displace( the following error message invalid ser name pleasetry again.

A thentication( Application displace( the following error message invalid password please tryagain.

A thentication( Application displace( the following error message invalid ser name andinvalid password please try again.

Application clears all the fields login screen and displaces the c rsor in the ser name fields.

Application clicks the login screen.

7uide line to be followed by test engineers soon after the recei+e the document :"

6dentify the mod le to which the se case belong toL

Ans: Sec rity mod le

6dentify the f nctionality of the se case with respect total f nctionality L

Ans : A thentication .

6dentify the f nctionality point and prepare the f nctionality point doc mentL

Ans: 3her e ever ser perform some actions on the application that is called f nctional point.

6dentify the inp t re! irement to perform testing L

Ans: >alid and invalid ser name and password .

6dentify the actors invalid L

Ans: @ormal ser and admin ser.

6dentify the weather the se case linked with any other se case L

33


34/50

Ans: /ome pager and admin page se case.

6dentify the preconditionL

Ans: 0ogin screen m st be available

6dentify the post condition L

Ans: ither home page and admin ser and error.

nderstand main flow of the application L

nderstand the alternative of the applicationL

nderstand the special re! irement L

#oc ment the test cases for the main flow L

#oc ment the test cases for the alternative L

#oc ment the test cases of special re! irementL

Prepare the traceability matri9 +or) c rser reference matri9L

unctional point :" "he point where the ser can perform some action in the application isknow as f nctional point.

%esting process related document:"

%raceability matrix :" 6t is a doc ment which contains table of linking information sed fortraceability back for the reference in any kind of conf sion +or)! estionable sit ation.

&B1:" +(%6) 7omplete "raceability 1atri9.

(/*

G

'

% /*

H

33

% /*

'

%(/*

1F

G'

*/*

D

G

34

UCD

Use Case

Docume

nt

FPD

Function

al Point

Docume

TSD

Test

Scenario

Docume

DTCD

Detail

Test

Case

DTD

Defect

Point

Docume


35/50

DF GF H5 55 H

&BD:" 2%6 = :e! irement "raceability 1atri9 ).

%(/*

1

D

G

H

5

2&Q /2&6% /*

1.F

1.F

D.F

D.F

G.F

&BG:"*%6= #efect "raceability matri9 ).

%ype of test case:" "est case are broadly divided in G types.

35

*%*

1

D

G

5

%(/*

D.G

H.'

,.5

.5


36/50

i) = 6 test case

ii) ; nctional test case +two types)

a) M>e test case

b) N>e test case

iii) @on,; nctional test cases

7uide line for the writing 7 / test case:"

Any idea a test engineer with which he feels that we can test something with o t doing anyaction will follow nder = 6 test case.

&B:"

7heck for the available of all the object .

7heck for the consistence for the object.

7heck for the allayment of the object

6f at all the c stomer re! irement are given.

7heck for the spelling and grammar.

7uide line for the writing the I e test case:"

"est engineer sho ld have M>e mind set.

/e sho ld consider the M>e flow of the application

/e m st se only the valid inp t from the point of the f nctionality.

36


37/50

37

ui

ment

%est

case/d

7CCB

7CC2

7CCD

7CCG

7CCH

7CCI

(ategory

M>e

= 6

= 6

= 6

= 6

= 6

rere

uisite

,@A,

,@A,

,@A,

,@A,

,@A,

,@A,

*escriptionJ%est steps

6nvok e theapplication.

7heckfor the

availa bilityof alltheobjective inloginscreenas forthe-$% .

7heckfor thecanonistic ofall theobjectin theloginscreen.

7heckfor the

spelling intheloginscreen.

7heckfor theinitial

position ofthec rsor .

7heckfor theenable

propriety oflogin(

&xpected +alue

0oginscreensho ld bedisplay

All the

objectm st beavailableloginscreen asfor the-$%.

All theObjectsm st beconsistentwith eachother.

All thespellingm st becorrect.

6nitiallythe c rsorm st

position inthe sername.

6nitiallylogin(clearly

b ttonm st bedisableand cancle

b tton

%est data

-$%

Actual +alue

0ogin screen isdisplay.

All the objectsavailable as perthe -$%

All the object areconsisted witheach other

All the spellingare correct.

6nitially thec rsor position inthe connect tofields.

0ogin( clear(cancel b tton areto enable.

7lear b tton isenable.

2esut

Pass

Pass

Pass

Pass

;ail

;ail


38/50

-$%=-ogin $b!ect %able):"

/% = alid /nput %able )

38

.#o

B

2

D

G

H

I

$b!ect #ame

ser name

Password

7onnect to

0ogin

7lear

7ancel

$b!ect %ype

"e9t bo9

"e9t bo9

7ombo bo9

* tton

* tton

* tton


39/50

.#o

1

D

G

H

5

'

ser #ame

S resh

@ag

7hir

@tr

>enky

Admin

assword

%"P

Amal

Sridevi

*alakrishna

6ll

Admin

&xceptedalue

Admin page

/ome page

/ome page

/ome page

/ome page

Admin page

Actual alue

Admin page

@ag home page

7hir home page

@tr home page

>enky home page

Admin page

2esult

Pass

Pass

Pass

Pass

Pass

Pass

/ /%=/n+alid /nput %able)

.#o

1

D

G

H

ser #ame

S re

7hir tha

@tr

@ag

assword

%tp

Sridevi

*alakr

"ab

&xpectedage

6nvalid sername pl< trayagain

6nvalid sername pl< trayagain

6nvalid password plalB

>al2

:es lt

A::

>al B

>al 2

:es lt

10

20

*10


45/50

6inor *efect $,6f at all the problem some related to the and feel of the application then s ch type of problem are treated as minor defect.

9$,

uggestion :" 6f at all the problem are related to the val e of the application then s ch type of problems are treated as s ggestion.

9$, M>e

@ot ser friendly message

ser friendly

message

riority :" Priority describes the se! ence in which defect need to be rectify.

Priority is classified in to H types.

i) 7ritical +or) pri B+or) pB

ii) /igh +or) pri 2+or) p2

iii) 1edi m +or)pri D+or)pD

iv) 0ow +or) pri G+or) pG

45

::

>al B

>al 2

:es lt

BAD

@

6nvalid entry please tray again

6nvalid entry please enter M>e integer


46/50

=enerally the fatal defect will be given critical priority( major defect will be given( high priority( minor defect will be given medi m priority( b t dependence on the sit ation prioritywill be changed.

-ow se+erity high priority case:"

3hen ever there is a c stomer visit all the loo8 and feel defects will be given highest priorityeven tho gh they are less serio s.


47/50

#ew:" 3hen ever the defect is newly identified by the test engineer then the stat s is new.

$pen:" 3hen ever the developer the accepts then

*eferred:" 3hen ever the developer the accepts the defect b t wants some time for rectifyingthe defect the will set the stat s is deferred.

ixed: , 3hen ever the defect is rectified the developer will set the stat s as fi9ed.

2eopened and (lose: , Once the ne9t b ild released the test engineer will check whetherdefect is relay rectified +or)not if at all they feel relay rectified then they will set the stat s asclosed other wise reopened.


48/50

"ester #evelopers

*raw @ac8:"

:ed ndancy

"ime cons ming

@o transparency

@o sec rity

(ommon repository oriented bug repotting process:"

"est lead 7ommon repository #evelop lead

@ug trac8ing tool oriented @ug 2eporting process :"

7ommon repository

48

@%%


49/50

@ug trac8ing tools :" * g tracking tool is soft ware application which can be accessed only by theetheri


50/50

Documents

Complete Guide to Manual Testing@Kumar