completeguidetomanualtestinguma-120608233901-phpapp01.doc

8/18/2019 completeguidetomanualtestinguma-120608233901-phpapp01.doc

1/52

MANUAL TESTING

1) Q. Why did you choose testing ?

Ans: 1) Scope of getting the job is very very high.

2) No need of depend upon any technology.

3) Testing is going to be there forever.

4) I want consistence through out my life.

2) Q. What exactly we need to get a job?

Ans !) Stuff

") #ommunication s$ills %reading& writing & spea$ing& lesion'

() #onfidence

4) ynamism

3) Q. Why explicitly the test engineers are been recruiting in to the sotware

co!panies?

Ans: !) *nce person cannot perform two tas$s efficient at a time.

") Sentimental attachments.

") Q. Who can get testing job?

Ans: Any graduate who is creative can get testing job very easily

#) Q. Why explicitly the testing engineers are been recruited into the sotware

co!panies?

Ans: 1) *ne person can+t perform two tas$ efficiently at a time.

") Sentimental Attachment.

$%&'(*:+

,roject is something that is developed based on the particular customers

re-uirements and used by that particular customers only.

$%&,-*:+

1


2/52

,roduct is something that is developed base on the companies specification

and used by the multiple customers.

&*(:+ The company will decide the specification by pic$ing the common re-uirements of

customer.

/) Q.lassical deinition o 0uality?

Ans: uality is defined has justification of all the re-uirements of a customer in a product.

&*(: uality is not defined in the product it is defined in the customer mind.

,((*: efect is defined as deiation from the re-uirements.

) Q. 4atest deinition o 0uality?

Ans uality is defined as not only the justification of the re-uirements but also presence of

the value %alue ..means ..user riendly'

5) Q. What is testing?

Ans Testing is a process in the defects are 6dentiied7 6solated%separately'/8ubject or

%ectiication%sending' 0nsure that the product is defect free in order to produce a -uality

product in the end and hence customer satisfaction.

9)Q. What is bidding the project?

Ans 1idding the project is defined as re-uest are proposal/ estimation and signing

off2official3agreement).

6 & ;((*6


3/52

:ill be involved in this meeting.

&*(:+ Apart from this meeting any other start up meeting in also called as ; =ic= o

!eeting $roject 6nitiation ote:+ $6 It is a mail prepared by the projectmanager and sent the #0* of software company as well as to all of his core

team members in order to intimate then that they are about to start the actual

project activities.

#0*=#hief 0>ecutive *fficer

#**=#hief *f *fficer

8,4 >8otware ,eelop!ent 4ie ycle:+

It contains / ,hase

• Initial or ?e-uirement ,hase

• Analysis ,hase

• esigned ,hase

• #oding ,hase 2or) ,rogramming phase

• Testing ,hase

• eliver and maintenance ,hase

6nitial or %e0uire!ent $hase:+

*as=:+Interacting with the customer and gathering the re-uirements.

%oles:+ i) 1usiness Analyst %1A'

ii) 0ngagement manager %08'

$rocess:+ @irst of all the 1usiness Analyst can Appointment . from the customer/ collects the

template from the company meet the customer an the appointment date gathers the

re-uirements with the help of the template and come bac$ to the company with the

re-uirement documentary.

The 0ngagement manager will go through the re-uirements document. If at all he

finds any e>tra re-uirements hence he will deal with the e>cess cast of project. If it is any

confession of re-uirements then the will as$ the consult team to develop the prototype he

will demonstrates to the customer gather the clean re-uirements and finally hand over the

re-uirements document to the business analyst.

3


4/52

$roo:+ ,roof of this phase is ;%e0uire!ents ,ocu!ent@.

This document is called with different name in different companies

@?S 2@unctional ?e-uirements Specification)

#?S 2#lient or #ustomer ?e-uirements Specification)

5?S 25ser ?e-uirements Specification)

1 21usiness esign ocument)

1 21usiness ocument)

1?S 21usiness ?e-uirement Specification)

&*(:+Some companies may maintains two documents in the initial phase/ one is for igh

leel business low inor!ation and the other in for ,etail unction inor!ation.

1ut some companies may maintains both the intimation in a single docu!ent.

*e!plate:+ Template in a predeined or!at which is used for preparing the

document easily and perfectly

$rototype:+ ,rototype is a roughly and rapidly developed model which is

used is for demonstration to the customer in order to gather the clear

re-uirement and also to win his confidence of the customer.

Analysis phase:+

*as=:+

• @easibility study

• Tentative planning

• Technology selection 9 0nvironment conformation

•?e-uirement analysis

%oles:+

• System Analyst %SA'

• ,roject 8anager %,8'

• Team 9Technical 8anager %T8'

$rocess:+

4


5/52

easibility study:+ Bpossibility) It is a detailed study conducted on re-uirement in order to

conform whether all of those re-uirements are possible with in the given time budget and

resources are not.

*entatie planning B*e!porary):3 The resource planning as well as scheduling will be

temporary planned section.

*echnology selection C (niron!ent conor!ation:+ The list of all the technologies that

are re-uired to accomplish this project successfully will be enlisted as well as the client

environment will be conformed here in this section.

%e0uire!ent analysis:+ The list of all the re-uirements that are re-uired by the company

li$e human resource / software and hardware to accomplish that project /successful will be

enlisted and mentioned here in this section.

$roo: The proof document if the analysis phase is 8%8 B8yste! %e0uire!ent8peciication )

,esigned $hase:+

*as=:+ i) 6igh 7evel esigning %67'

ii) 7ow 7evel esigning %77'

%oles:+ i) #hief architect 2#A) is responsible for high level designing.

ii) Technical 7ead 2TA) is responsible for low level designing.

$rocess:+ The chief architect will divided whole project into modules /by drawing some

diagrams using a language -;4B5nified 8odeling 7anguage)

The technical lead will divided the modules into sub modules by drawing some

diagrams using the same -;4.

Apart from this ta$es


6/52

%oles:+evelopers 2or) programming

$rocess:+ The developers will develop the actual source code with the support of technical

design document as well as by following the coding standards.

(xa!ple or coding standards:

,roper indentation

#olor coding.

,roper commenting.

$roo:+ The proof document of the coding phase 8, B8ource ode ,ocu!ent).

*esting phase:+

*as=:+ Testing

%oles:+ Test engineers

$rocess:+

Test engineers will receive the re-uirement document and will start

understanding the re-uirement.

:hile understanding the re-uirement if at all the get any doubt then they will

list out all the doubt in the re0uire!ents clariication note and will send it tothe author of the re-uirement doubt DAB1usiness Analyst).

*nce the clarification are given if still more clarification are re-uired then they

will conduct a reiew !eeting and will get all the clarification.

*nce all the re-uirement are clearly understood then they will ta$e the *est

case te!plate and will write the test cases.

*nce the 1st 1uild is released they will e>ecute the test cases.

If at all any defects are found they will list out then in the deect proile and

will send it to the development department .

*nce the ne>t 1uild is released they will re e>ecute the re-uired test case.

If at all any more defect are found they will update the defect profile and will

send it to the development department.

*nce the ne>t 1uild is released the same process will be continued.

This process will be continued again and again till the product is deect ree.

6


7/52

$roo:+ The proof the testing phase is Quality $roduct .

*est ase:+ If is an Idea of test engineer to test something based on the

re-uirements.

,eliery C ;aintains $hase:+

,eliery:+

*as=:+ 6and overring the application to the client .

%oles:+ eployment 0ngineers or Installation 0ngineers

$rocess:+ eployment engineers will go to the clients place / install the application into the

original customer /0nvironment and finally hand over+s the software to the customer.

$roo:+ The final oicial argu!ent !ade between the co!pany and the customer is the

proof document this phase.

;aintains:+ *nce the customer start using the application if at all any problem occurs then

that problem will become the tas$ /based on the tas$ corresponding roles will be appointed

/these roles will define the process/ solves the problem and final get the Application latter.

Some customer many re-uest for continuo+s maintenance in that situation the

company will send a team of member to the customer place continuously in order to ta$e care

of that sotware.

Q. where exactly testing co!es in to picture?

Which sort o testing you are expecting?

ow !any sort or testing are there?

Ans3 They are two sort of testing

i) 5n convectional testing.

ii) #onvectional testing.

-n conectional testing:+ It is a sort of testing in which the 0uality assurances people. :ill

chec$ each and every role in the organiation in order to conform weather they are doing

their wor$ according to the companies proper guidelines are not. ?ight form the staring of the

8,4 to the end of it.

onectional testing:+ It is a sort of testing in which the test engineers will chec$ the

developed application 2or) its related parts are wor$ing according to the e>pectation or not

from the coding phase to the end of the ;8,4<

7


8/52

;ethods o the testing Bor) testing techni0ues:+

1asically there are two methods of testing.

i) 1lac$ 1o> testing.

ii) :hite 1o> Testing 2or) Blass 1o> Testing 2or) #lear 1o> Testing

Dlac= Dox *esting:+ It is a method of testing in which one will perform testing only on the

unctional part of an application with out on the having the $nowledge of structural part.

5sually the blac$ bo> *est engineers will perform it.

White Dox *esting:+ It is a method of testing in which one will perform testing on the

8tructural part of an application .

5sually developers 2or) White box testers will perform it.


9/52

In this stage the Dlac= box test engineers will test the functional part of the

module.

6ntegration leel testing:+ In this stage the developers of will develop some

interaceBlin$ing program) in order to integrate the modules this interface will be tested by

white bo> testers. evelopers will follow any one of the approaches white integration the

module.

Top down approaches

1ottom up approaches

6ybrid approaches 2or) Sand rive approached

1ig31ang approaches

*op down approaches:+ In this approaches the parent modules will be

developed first and then the corresponding child modules will be developed

and integrated.

8*-D:+ :hile integrating the modules in top down approach if at all any !andatory

!odules are !issing then that mandatory modules will be replace with a te!porary

progra!.

9


10/52

Dotto! up approach:+ In this approached the child modules will be

developed first and will be integrated to the corresponding parent modules.

,%6E(%:+ :hile integrating the module in bottom up approached if at all any !andatory

!odules is !issing then that modules is replaced with a temporary program ;?IC0?<

ybrid approach Bor) 8an drie approach:+ This a mi>ed approach of 1oth

top down and bottom up approaches.

10


11/52

Dig+Dang approach:+ In this approach one will wait till all the modules are

developed and finally will integrate then at a time.

8yste! leel testing:+

8yste!:+ *nce the software application is installed in to an environment then as a whole we

will call it as a system.

In this stage the bloc$ bo> test engineers will conduct many type of testing li$e

load testing/ performance testing/ stress testing/ comparability testing/ system integration

testingDD..ect.

8yste! integration testing:+ It is a type of testing in which on will perform

some action on module and chec$ for the reflections in all the related are as of

the application.

-ser acceptance leel testing:+ In this stage the bloc$ bo> test engineer will perform testing

on the user desired areas in the presence of accept the application happy.

(niron!ent:+

0nvironment defined as group of hardware compounds with some basic

software 2&8) where one can install the $resentation 4ogic7 Dusiness 4ogic7 ,ata Dase

4ogic.

%or'

0nvironment defends as combinations of three layer that is $resentation

4ayer7 Dusiness 4ayer7 ,ata Dase 4ayer. :here once can install the $resentation 4ogic7

Dusiness 4ogic7 ,ata Dase 4ogic.

11


12/52

*ype & (niron!ent:+

Stand Alone 0nvironment 2or) *ne Tier Architecture.

#lient Sever 0nvironment 2or) Two Tier Architecture.

:eb 1ased 0nvironment 2or) Three Tier Architecture.

istributed 0nvironment 2or) N3Tier Architecture.

8tand Alone (niron!ent Bor) &ne *ier Architecture:+

In this environment only one tier will be there. ,resentation layer/ business layer/ data

base layer will be present in the same tier.

:hen ever the application need to be used by single user at time

then environment will be suggested.

lient 8eer (niron!ent Bor) *wo *ier Architecture:+ In this environment two tier will

be there .one is for client and another is for data base server. ,resentation layer and the

business layer will be available is each and every client and the data base player will be

present in data base server.

:hen ever the application need be used single premises and there is no

problem with the security of the. 1usiness logic as well as the application need accessed very

fast lye then this environment be suggested.

12


13/52

Web Dased (niron!ent Bor) *hree *ier Architecture:+ In 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

base sever. presentation layer available in the client business layer will be available in the

application server. data base sever.

:hen ever the application need to be used all over the world by limited

numbers of user and wounds the business logic will be secured and function updaters to beeasily them the in environment can be suggested.

13


14/52

W(D 8(%E(% 3 :eb server is a software which provides web services to

the client.

(F3 IIS2Internet Information Services)

,istributed (niron!ent Bor) +*ier Architecture:+This environment is same as webenvironment more the one application sever is introduced in separate hers in order to

distributed the load and increase the performance.

:hen ever the application needs to be use by huge number of user then this

environment can be suggested.

*6 46(*:+ If at all the client machine is having only the .presentation

logic then it is $now as thin client.

*6 46(*:+ If at all the client machine is having both presentation

logic as well as business logic then it is $nown as thic$ client.

A$$46A*6&:3 It is a ,resentation 7ayer/ 1usiness 7ayer/ ata 1ase

7ayer.

8&*WA%( ,(E(4&$;(* $%&(88 ;&,(48:+

:aterfall 8odel

,rototype 8odel

0volutionary 8odel

Spiral 8odel

@ish 8odel

C38odel

14


15/52


16/52

Adantage:+ when ever the customer is not clear with his re-uirement. Them this is best

suitable model

,raw Dac=:+ Is not a compiled develop process model.

It+s a still time consumer model.

#ompany should where the cost of prototype

5ser may limit re-uirement by stic$ing into the project.

(olutionary ;odel:+

16


17/52

A$$LICATION

BASE

LINE

Adantage:+ when ever the customer is evolution the re-uirement then this is the 1est

suitable model

,raw Dac=:+ time consuming model

#ostly model

eed lines can+t properly define.

No transference.

,roject monetary any maintenance is very difficult.

8piral ;odel:+

17

INITIAL

RE.

DEVELO$

A$$LICATIO

N

USER

VALEDATION

'EED BAC%

#IT! NE# RE.

USER

ACCE

$T

N

O

YE

S


18/52

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

4(RE'INIG &

$LANNING 2( RIS% ROOT

'OR T!E NET CYLE CAUSE

ANALYSIS

ESTIMATION

3( IM$LEMENATION

CONTINGENCIES

Adantage:+ :hen ever the project highly ris$ based then this is the best suitable model.

,raw Dac=:+ Time consuming model.

#ostly model.

?is$ root cause analysis is nota easy tas$.

ish ;odel:+

18


19/52

RE ANAYSIS DESIGN CODING

DELIVERY MAI*GAT!ERING SYSTEM

T+-/ 8aintan

SRS !LD SCD

BRS REVIE# LLD

BLOC% B T+-/

T+- S"#

SRS REVIE# TDD REVIE# #!IT BO TESTING

C/+

Adantage:+ As both the verification are done the outcome will be a -uality product.

,raw Dac=:+ Time consuming.

#ostly model.

E+;odel:+

Cerification Calidation

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 TEST

MANAGEMT $ROCESS USER ACCE$TANCE TESTING

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

A D++- /: ;< -+ -+-/ -+=.

19


20/52

B D++- >+: ;< -+ -=+>.

Adantage:+ As both the verification and validation is done and test management process is

maintained. The outcome will be -uality product.

,raw Dac=:+ It is time consuming model.

It is a costly model.

Eeriication:+ Cerification is a process of chec$ing whether the product is being

developing in a right manner or not.

Ealidation:+ Calidation is a process of chec$ing whether the develop product is right

or not.

*G$( & *(8*6ploratory testing

• 0nd3To30nd Testing

• Security testing

• 5sability testing

• ?eliability testing

• 8utation testing

• Adhoc testing

20


21/52

Duild acceptance testing Bor) Duild eriication testing Bor) 8anity testing:+

It is a type of testing in which one will conduct overall testing one the released build in

order to conform where the proper of not for conducting detailed testing

In this type of testing us ally they chec$ the following.

i) :eather the build can be properly installed in to environment or not

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

iii) :eather all the important feature are available or not.

iv) :eather all the re-uirement connections are properly established or not.

In some company they will call this types of testing as 8!o=e testing also

but in some companies they say that just before releasing the build the developer will chec$

weather the build is proper or not i.e. $now as 8!o=e testing.

*nce the build is released the testing engineers will once again chec$ weather

the build is proper or not i.e. $nows as 1AT 2or) 1CT 2or) sanity testing.

%egression testing:+ It is a type of testing in which one will perform testing on the ready

testing functionality again and again us allay it is done in two servicers.

i) :hen even some defects are identified raised to the development department once

the ne>t build is released the testing engineers will chec$ the defect functionality as

well as the related functionality once again.

ii) :hen ever some new feature are added i.e. the application ne>t build is released to

the testing department then the test engineers will chec$ all the related feature+s of

those new feature+s once again.

&*(: + Testing new features for the first time not regression testing.

Some companies may do %ando! testing at the end that also will fall under

regression testing only.

%etesting: + It is a type of testing in which one will perform testing on the same functionality

again and again with multiple sets of data in order come to a conclusion weather thefunctionality is wor$ing fine or not.

21


22/52

&*(:+

i) ?egression testing starts form the 2nd build and continue up to the last build.

ii) ?e testing starts from the 1st build and continuous up to the last build.

iii) uring regression testing also re testing will be conducted that is the reason

some people even call it as %e and %egression testing.

al testing: + It is a type of testing user accepting testing conducting in the soft ware

company by the test engineers just before the delivery.

D+testing: + It is a type of testing user accepting testing conducting in the client place either

by the end user 2or) by the third party testing e>perts just before actual implementation of a

application.

8tatic testing: + It is types of testing in which one will perform testing on the application on

its related factors without perform any action.

0E 3 B5I testing/ ocument testing/ code33333333333333ect

,yna!ic testing: + It is types of testing in which one will perform testing on the application

on its related factors by perform some action.

0E 3 retesting/ functionality testingDD.ect.

6nstillation testing :+ It is a type of testing in which one will trey to instillation the

application by following the guide ling provided in the deploy!ent docu!ent in order to

conform whether those guidelines really suitable for instillation the application comfortable

2or) not.

o!patibility testing:+ It is type of testing in which one will install the application into

multiple environment prepared with different .combation in order to chec$ .whether it is

suitable with those environment 2or) not.

;on=ey testing: + It is type of testing in which one will intentionally perform some action

in order to chec$ stability of the application.

$ort testing: + It is type of testing in which one will install the application into the original

customers environment and chec$ whether it is comprisable with that environment 2or) not.

22


23/52

(xploratory testing:+ It is type of testing in which ,o !any expert will chec$ the

functionality of the application which out having the $nowledge of re-uirement just by

parallel e>ploring the functionality.

(xploratory: + 6ave in the base $nowledge of some concept doing something and

more about it is $nows as e>ploratory.

(nd+*o+(nd testing: + It is type of testing in which one will perform testing on all the end to

end sceneries of the application.

0>3 login

1alance en-uiry 3333!F/FFF

:ith draw 3333333(/FFF

1alance stmt 3333333333G/FFF

7ogout

8ecurity testing3 It is type of testing in which one will perform testing on the application in

order to conform whether it is properly protected 2or)not.

i) Authentication testing : It is a type of security testing in which one will enter

different combination of user names and password .and chec$ whether only

authoried people are able to access the application 2or)not.

ii) ,irect -%4 testing: It is type of security testing in which one will enter the direct

5?7+s if secured pages and chec$ whether they access 2or) not.

-%4 >-nior! %esource 4ocation

iii) ire wall lea=age testing Bor )-ser realiHed testing :+ It is type of testing in

which one will enter into the application as a authoried user and will try to access

bye and his limited in order to conform whether he can access 2or)not.

-sability testing:+ It is type of testing in which one will chec$ the user friendly of the

application.

%eliability testing Bor ) 8oc=ing testing:+ It is type of testing in which one will use the

application continues for long period of time in order to set the stability of the application.

;utation testing:+ It is type of testing in which one will perform testing on the application or

its related factors after doing some changes to them.

Adhoc testing3It is a type of testing in which one will perform testing on the application in

the there own style after understanding re-uirement very clearly.

5s ally this type of testing will be encouraged after formal testing.

23


24/52

8&*WA%( *(8*6< 46G G4( B8*4):+ 8*4 contain / phase

i) T0ST ,7ANNINB

ii) T0ST 0C070,*80NT

iii) T0ST 0E0#5TI*N

iv) ?0S57T ANA7HSIS

v) 15B T?A#INB

vi) ?0,*?T

*est planning:+ Test plan is strategic document which contains some information that

describes how to perform testing on that application in a effective /efficient and optimied

way.

$lan:+ ,lan is a strategic document which contain some information that describe how

to perform tas$ in a effective/ efficient and optimiation.

&pti!iHation:+ *ptimiation is a process are utiliing the available resources to their

level best and getting the ma>imum possible out put.

6ndex o test plan Bor) ontents o test plan:3

!.F) Introduction

!.!) objective

!.") reference document

".F) #overage testing

".!) features be testing

".") features not be testing

(.F) Test strategic

(.!) levels of testing

(.") type of testing

(.() test design techni-ues

(.4) configuration management

24


25/52

(.) test metrics

(.J) terminology

(.G) automation plan

(.K) list of automated tools

4.F) 1ase criteria

4.!) acceptance criteria

4.") suspension criteria

.F) Test deliverables

J.F) Test environment

G.F) ?esources planning

K.F) Scheduling

L.F) Staffing and training

!F.F) ?is$ and consistencies

!!.F) Assumption

!".F) Approval information

1.I) 6*%&,-*6&:+

• &bjectie: + ,urpose of the document will be clearly described here in this

section.

• %eerence docu!ent:3 The list of the document that are referred will

preparing this documents will be listed out here in this section

(F: 3 S?S/ ,roject plan

2.I) &E(%A


26/52

iii) @eatures that are planed to be incorporated in feature

iv) @eatures that are s$ipped based on the time constrains.

3.I) *(8* 8*%A*(


27/52

• 4ist o auto!ated tools: + The list of all the automated tools that are used in that

company will be listed out here in this section.

".F) Dase criteria:+

• Acceptance criteria: + :hen to stop testing will be clearly described in this section.

• 8uspense criteria: + :hen to suspense testing will be clearly described here in this

section.

#.I) *est delierables: + The list of all the document that are to be developed of delivery

doing testing process testing process will be mentioned here on this section.

J.F) *est eniron!ent3The details of environment that is about to be used for testing will be

clearly mentioned here in this section.

G.F) %esource planning:+ :ho has to do what will be clearly described here in this section.

K.F) 8cheduling Bor) *i!e planning:+ The starting dates and ending dates of each and ever

tas$ will be clearly planed and mention in this section.

L.F)8taing and training:+ To accomplish that project sues fully if at all any staff

re-uirement and if at all any training re-uirement then that detailed will be clearly mention

here in this section.

!F.F) %is= and ontinence3 This list of all the potential ris$ and continence solution plan

will be clearly mentioned here in this section.

0>3 0mployee may leave the company the middle of the projectM

Ans. 0mployee need to mint on benched.

5nable to de clearly project with in the deadline projectM

Ans. ,roper plan insurance.

#ostumer may impose the deadlineM

Ans. :hat not be tested should planned.

5nable to test all the feature with in the given timeM

Ans. ,riority based the e>ecution.

!!.F) Assu!ptions: + The listed of all the thin$ that are be assumed by the test engineer will

be clearly mentioned here in this section.

!".F) Approached inor!ation:+ :ho has approval this document when it is approval will

be clearly described in this section.

27


28/52

ii)*est deelop!ent phase:+

%e0uire!ent ,ocu!entation

4 -8( A8(8

-se cases:+ 5se case describes of the functionality of certain application terms of

action response.

4ogin

i) unctional re0uire!ent

ii) 8pecial re0uire!ent

unctional re0uire!ent:+

7ogin screen should contain user name/ password connect to fields login/ clear/ cancel

button.

#onnect fields is not mandatory but it should be allow user to select the data base option

when ever re-uire.

5pon entering valid user name/ password and clic$ing on login button corresponding

page must be displayed.

5pon entering in to any of the fields and clic$ing on clearly button all the fields must be

cleared and courser should he display in the user name.

5pon clic$ing on cancel button login screen must be closed.

28

HLI

L L I

SCREEN

SHORT

-ser a!e

$assword

4ogin lear ancel


29/52

8pecial re0uire!ent:+

Initial when ever the login page invo$ed login and when ever and clear button is

disabled.

#ancel button must be all ways enable.

5pon entering some information in to and of the fields clear button must be enabling.

5pon entering some information in to both user name and password field+s login

button must be enabling.

Tabbing order must be user name/ password/ connect to/ login/ clearer/ cancel.

-se case te!plate:+

i) Name of the use case

ii) 1rief description of the use case

iii) Action in valued

iv) Special re-uirement

v) ,re condition

vi) post condition

Cii)@low condition

-se ase ,ocu!ent3

a!e o the use case:+

i) Name of the use case 7ogin use case

ii) 1rief description the use case This use case describes the functionality of all the

features present in the login screen.

iii) Actors involved or!al user and Add !ine user.

i) Special re-uirement two types

0>plicitly re-uirement

Implicitly re-uirement

(xplicitly re0uire!ent:+ The re-uirement the e>plicitly given by the customer are $now

as e>plicitly re-uirement.

29


30/52

6!plicitly re0uire!ent: The re-uirement that are analyed by the business analyst which

will add some value to the application with out disturbing any of the original customer

re-uirements.

(xplicitly re0uire!ent:+

Install when ever the login page invo$ed login and clear button is disables.

#ancel button must be any way enable.

*pen entering some information into any the field+s clear button must be enabling.

5pon entering some information into both user name and password field+s login button

must be enable.

Tabbing order must be user name password connect to login clear cancel.

6!plicitly re0uire!ent:+

*pen entering invalid user name valid password and clic$ on login button the following

error message must be displayed. ;Invalid user name please try again


31/52

Actors clic$ on cancel button.

%esponse

Application display the login screen with the following fields user name/ password/ connect

to/ login/ clear/ cancel.

Authentication/ application display either home page 2or)admin page depending upon the

actor entered.

Authentication/ application display either home page 2or)admin page depending upon the

actor entered with the mentioned data base connections . Bo to Alternatie low *able 1 2Invalid user name)

Bo to Alternatie low *able 2 2invalid password)

Bo to Alternatie low *able 3 2invalid user name and password).

Bo to Alternatie low *able " 2clear clic$).

Bo to Alternatie low *able # 2cancel clic$).

31


32/52

Alternatie low *able 1:+

Action

Actors enters invalid user name valid password and clic$ on login button.


Actors enters in valid password valid user name and clic$ on login button.


Actors enters invalid user name invalid password and clic$ on login button.

Alternatie low *able ":+

Actors enter some information into any of the fields and clic$ on clear button.


Actors clic$ on the cancel button.

32


33/52

%esponse

Authentication/ Application displace/ the following error message invalid user name please

try again.

Authentication/ Application displace/ the following error message invalid password please try

again.

Authentication/ Application displace/ the following error message invalid user name and

invalid password please try again.

Application clears all the fields+ login screen and displaces the cursor in the user name fields.

Application clic$s the login screen.


34/52

Identify the weather the use case lin$ed with any other use case M

Ans: 6ome pager and admin page use case.

Identify the preconditionM

Ans: 7ogin screen must be available

Identify the post condition M

Ans: 0ither home page and admin user and error.

5nderstand main flow of the application M

5nderstand the alternative of the applicationM

5nderstand the special re-uirement M

ocument the test cases for the main flow M

ocument the test cases for the alternative M

ocument the test cases of special re-uirementM

,repare the traceability matri> 2or) curser reference matri>M

unctional point :+ The point where the user can perform some action in the application is

$now as functional point.

*esting process related docu!ent:+

*raceability !atrix :+It is a document which contains table of lin$ing information used for

traceability bac$ for the reference in any $ind of confusion 2or)-uestionable situation.

(F1:+ 2*;) #omplete Traceability 8atri>.

34

UCD

Use Case

Document

FPD

Function

al PointDocume

TSD

Test

ScenarioDocume

DTCD

Detail

TestCase

DTD

Defect

PointDocume


35/52

-6,

3

/

2I

*$6,

"

99

3I

*86,

5

5/

"#

*6,

1I

3/

##

,6,

2

3

"

(F2:+ %*; B ?e-uirement Traceability 8atri>).

*6,

1

2

3

"

#

%(Q-6%(;(* 6,

1.I

1.I

2.I

2.I

3.I

(F3:+,*;Befect Traceability matri>).

*ype o test case:+ Test case are broadly divided in 3 types.

i) B5I test case

ii) @unctional test case 2two types)

a) &Ce test case

35

,*,

1

2

3

#

*6,

2.3

"./

.#

5.#


36/52

b) Ce test case

iii) Non3@unctional test cases


37/52

#FF"

#FF(

#FF4

#FF

#FFJ

#FFG

B5I

B5I

B5I

B5I

B5I

B5I

3NA3

3NA3

3NA3

3NA3

3NA3

3NA3

bility

of all

the

object

ive in

login

screen

as for

the

4&*.

• #hec$

for the

canoni

stic of

all the

object

in the

loginscreen

.

• #hec$

for the

spellin

g in

the

login

screen

.

• #hec$

for the

initial

positi

on of

the

cursor.

• #hec$

for the

enable

propri

ety of

login/clear/

and

cancle

button

.

• 0nter

some

infor

matio

n into

any of

thefiled

available

login

screen as

for the

4&*.

• All the

*bjects

must be

consistent

with each

other.

• All the

spelling

must be

correct.

• Initially

the cursor

must position in

the user

name.

• Initially

login/

clearly

button

must be

disable

and cancle

button

must be

enabled.

• #lear

button

must be

enable.

• All the obje

consisted w

each other

• All the spel

are correct.

• Initially th

cursor posit

the connectfields.

• 7ogin/ clea

cancel butt

to enable.

• #lear butto

enable.

• 7ogin butto

enable.

37


38/52

#FFK

#FFL

#F!F

B5I

B5I

B5I

3NA3

3NA3

3NA3

and

chec$

for the

enable

priorit

y of

clear

button

• 0nter

some

infor

matio

n into

both

user

name

passw

ordfields

and

chec$

for the

enable

propri

ety of

login

button

.

• 0nter

theuser

name /

passw

ord/ as

for the

E6*

and

clic$

on

login

button.

• 0nter

the

user

name /

passw

ord/ as

for the

E6*

select

data

basedopecti

• 7ogin

button

must be

enable.

• #orrespon

ding page

be must be

displayed

as per

the E6*.

• #orrespon

ding page

be must be

displayed

as per the

E6* withthe

mentioned

data base

connectio

n.

• All the

fields

must becleared

E6*

E6*

• #orrespond

page displa

per the E6*

• #orrespond

page displa

per the E6*mentioned t

data based.

• All the field

clear but cunot display

the user na

• 7ogin scree

close.

• Tabing ordefollows use

password c

to login can

clear.

• #orrespond

error messa

not as per t

6E6*.

38


39/52

#F!!

#F!"

#F!(

#F!4

#F!

B5I

B5I

B5I

B5I

B5I

3NA3

3NA3

3NA3

3NA3

3NA3

on and

clic$

on

login

button

.

• 0nter

some

infor

matio

n into

any of

the

fields

and

clic$

on

clear button

.

• #lic$

in the

cancle

button

.

• #hec$ for the

tabing

order

of the

object

.

• 0nter

the

username /

passw

ord as

per

the

6E6*

and

clic$

on

login

button

.• 0nter

and curser

should be

displayed

in the user

name field

.

• 7ogin

screen

closed.

•

Tabingorder must

be

follows.

2user

name

password

connect to

login

cancle

clear )

• #orrespon

ding error

message

be display

as per

6E6*.

• 7ogin

button

must be

disable.

6E6*

• 7ogin butto

enable.

• 7ogin butto

enable.

39


40/52

#F!J

3NA3

some

infor

matio

n only

into

the

user

name

field

and

clic$

for the

enable

propri

ety

login

button

.• 0nter

some

infor

matio

n only

into

the

passw

ord

filed

and

chec$for the

enable

proper

ty

login

button

.

• 7ogin

button

must be

disable.

4&*B4ogin &bject *able):+

40

8.o

!

"

(

4

J

&bject a!e

5ser name

,assword

#onnect to

7ogin

#lear

#ancel

&bject *ype

Te>t bo>

Te>t bo>

#ombo bo>

1utton

1utton

1utton


41/52

E6* BEalid 6nput *able )

8.o

1

2

3

"

#

/

-ser a!e

Suresh

Nag

#hiru

Ntr

Cen$y

Admin

$assword

T,

Amal

Sridevi

1ala$rishna

Illu

Admin

(xcepted

Ealue

Admin page

6ome page

6ome page

6ome page

6ome page

Admin page

Actual Ealue

Admin page

Nag home

page

#hiru home

page

Ntr home

page

Cen$y home page

Admin page

%esult

,ass

,ass

,ass

,ass

,ass

,ass

6E6*B6nalid 6nput *able)

8.o

1

-ser a!e

Sure

$assword

tp

(xpected

$age

Invalid user

name pl tray

again

Invalid user

Actual Ealue

Admin page

%esult

@ail

41


42/52

2

3

"

#

/

#hirutha

Ntr

Nag

Ovreddy

5pendra

Sridevi

1ala$r

Tab

OC?

Anu

name pl tray

again

Invalid

password pl

tray again

Invalid

password pl

tray again

Invalid

password pl

tray again

Invalid user

name and

password pl

tray again

,l entry

valid user

name

,l entry

valid,assword

,l entry

valid

,assword

,l entry

valid 5ser

name

Invalid

password pl

tray again

pass

pass

,ass

@ail

@ail

pected value with actual values and

if both are matching they will decide result as pass other wise fail.

If at all the test if not e>ecuted then they will decide the result as bloc$ed.

Dug trac=ing:+ 1ug trac$ing is processes which defect are isolate7 identiy/ and !anaged.

42


43/52

,e

ect

1

2

3

*e

st

ca

se

6,

#F

F

#FFJ

#F

!!

6ssue

descript

ion

Initially

the

cursor is

position

ed in the

connect

to filed .

Initially

login

and

clear

button

are

enable

instead

of begin

display.

5pon

clic$ing

on clear

button

all the

field are

clear but

the

cursor is

nit

position

in the

username

%eprod

ucible

Not

applicab

le

Not

applicab

le.

P0ntersome

informat

ion any

of

fields.

Pclic$

on clear

button.

Pobserve that all

D

y

O

v

r

Ov

r

O

v

r

,

at

e

Du

ild

1

1

1

Eers

ion

2.3./

2.3./

2.3./

,ee

ct

8ee

rity

,ee

ct

$rio

rity

,eect

%esol

ution

ix

D

y

i

x

da

te

i

x

bu

ild

,at

a

lo

ser

43


44/52

"

#

#F

!4

#F

!

filed.

5pon

entering

user

name/

passwor

d as per

,6E*

and

clic$ing

on login

buttoncorrespo

nding

error

message

are not

display

as per

the

,6E*.

5pon

entering

some

informat

ion

the

fields

are

cleared

but the

cursor is

not

display

in the

user

name.

P0nter

user

name

,E6*.

M0nter

the

passwor d ,E6*.

M#lic$

on login

button

Pobserv

e that

correspo

nding

errormessage

is not

display

the

,E6*.

P0ntersome

O

v

r

1

1

2.3./

2.3./

44


45/52

/

#F

!J

*nly

into user

name

field

2or)

only

into

passwor

d filedlogin

button

is

enabled

misted

of

display.

only

into user

name

filed

only

into the

passwor

d filed.

P

observe

that

login button is

enable

instead

of being

display.

O

v

r

O

v

r

1 2.3./

,6E6*Befect Invalid Input Table)

45


46/52

8.o

1

2

3

-ser a!e

Suresh

5ma

5prndra

$assword

T,

Ovr

Anu

(xpect

,l enter valid

user name

,l enter valid

user name

9password

,l enter valid

user name

9password

Actual Ealue

,l enter valid

user name

,l enter valid

user name

,l enter valid

user name

,eect 6,:+ The se-uence of the defect no will be mentioned her in this section.

*est case 6,:3 The test case id based on the which defect is found will be mentioned her in

this section.

6ssue ,escription:+ :hat e>actly the defect is will be clearly described here in this section.

%eproducible stops:+ The list of all the step which are followed by the test engineer in

order to identify the feature will be mention here in this section.

,eection Dy:3 The name of test engineer who has the defect are defect in this section.

,eection ,ate:+ The date are on which will be mention her in this section.

,eection Duild:+ The build number in which the defect will be mention in this section.

,eection Eersion:+ The version number in which the defect is found will be mention in this section.

8eerity:+ Severity describes the severity of the defect severity is classified in to " types.

• @atal 2or) s! 2or) sev! 2or) !.

• 8ajor 2or) s" 2or) sev" 2or) ".

• 8inor 2or) s" 2or) sev( 2or) (.

• Suggestion 2or) s42or)sev4 2or)4.

atal:+ It at all the related to the navigational bloc$ on available by of main functionality then such

type of problems are treated as fatal defects.

0E3

46

,age

!

,age

"

,age

(

,age

4

N-

?+/

/

Cal!

Cal"

?esult


47/52

;ajor deect:+ If at all the problem are related to the wor$ing the major functionality them such type

of problem are treated a major defect.

0E3

;inor ,eect 3If at all the problem some related to the and feel of the application then such type of

problem are treated as minor defect.

0>3

8uggestion :+ If at all the problem are related to the value of the application then such type of

problems are treated as suggestion.

0>3 &Ce

Not user friendly message

47

A::

Cal !

Cal "

?esult

10

20

*10

::

Cal !

Cal "

?esult

BAD

@

Invalid entry please tray again

Invalid entry please enter &Ce integer


48/52

5ser friendly

message

$riority :+ ,riority describes the se-uence in which defect need to be rectify.

,riority is classified in to " types.

i) #ritical 2or) pri !2or) p!

ii) 6igh 2or) pri "2or) p"

iii) 8edium 2or)pri (2or)p(

iv) 7ow 2or) pri 42or) p4

Benerally the fatal defect will be given critical priority/ major defect will be given/ high

priority/ minor defect will be given medium priority/ but dependence on the situation priority

will be changed.

4ow seerity high priority case:+

:hen ever there is a customer visit all the loo= and eel deects will be given highest priority

even though they are less serious.

igh seerity low priority case:+

:hen ever some part of model if development/ reminding part is testing

department/ the test engineer will raise that part is fatal issue but the development will given

low priority given it.

Dug lie cycle:+

No

Hes

48

?e-uire

ment

eveloper

Application

Is defect

really

rectificati

on If

defect Stop the testing

Is it

really a

defect

?ectification

*pen

#losed New

6old

?ejected

As per design

Testing @i>edHes No


49/52

1uild ! 1uild "

Hes No

ew:+ :hen ever the defect is newly identified by the test engineer then the status is new.

&pen:+ :hen ever the developer the accepts then

,eerred:+ :hen ever the developer the accepts the defect but wants some time for rectifying

the defect the will set the status is deferred.

ixed:3 :hen ever the defect is rectified the developer will set the status as fi>ed.

%eopened and lose:3 *nce the ne>t build released the test engineer will chec$ whether

defect is relay rectified 2or)not if at all they feel relay rectified then they will set the status as

closed other wise reopened.

old:+ :hen ever the developer is configured to accept or reject the defect they will set the

status is hold.

:hen ever the defect is hold status as they will be a meeting on that defect 2Triage

meeting) and if at all consoled as a defect the developer will open it other wise the tester will closed it.

%ejected:+:hen ever the developer is conformed it is not a defect there he will status is

rejected.

:hen ever the defect is rejected status the test engineer will once again chec$ if at all he

also feels it is a not a defect then he will set the status as closed other he will reopened.

As per design:+ Bit is a rare case only)

49

?e opened


50/52

:hen ever the developer feels the tester has raised the defect with out having

$nowledge of latest re-uirement then he will chec$ the status as As per design.

:hen ever the defect in as per design status the test engineer will go to the new

re-uirement if at all he also feel it is as per design only then he will set the status is closed

other wise reopened.

%eporting phase:+

lassical Dug reporting process :+

Test lead evelop lead

Tester evelopers

,raw Dac=:+

?edundancy

Time consuming

No transparency

No security

o!!on repository oriented bug repotting process:+

Test lead #ommon repository evelop lead

50


51/52

Dug trac=ing tool oriented Dug %eporting process :+

#ommon repository

Dug trac=ing tools :+ 1ug trac$ing tool is soft ware application which can be accessed only by theetheried people which provides all the facility for bug trac$ing tools.

0E3 1ug illa/ issues trac$ing

*est closer Actiity :+ This a finely activity done in the process the test summary report which

contain some following information .

No.of cycles e>ecution.

evotion in of each cycle.

No.of test case are e>ecution in which cycle.

No.of test case are passed are failed .

No.of defect are found in each cycle and e>tra.

Way o testing:+ there or two type.

i) 8anual testing.

ii) Automation testing.

;anual testing3 8anual testing is a process in which all the phase of software testing life cycle li$e

test planning/ test development/ test e>ecution/ result analysis/ bug trac$ing and report or accomplish

successful manually with human efforts.

51

D**


52/52

,raw bac= o !anual testing:+

Time consuming.

7ess accuracy.

Tiredness.

Simulations action are all most impossible .

#on+t repeat the same tas$ again and again with some interest.

8ore no.of human resources are re-uired.

completeguidetomanualtestinguma-120608233901-phpapp01.doc

Documents

Transcript of completeguidetomanualtestinguma-120608233901-phpapp01.doc