c








 
 

Testing will be stopped when we came to know that there are only some minnor bugs which may not effect the
functionality of the application and when all the test cases has benn executed sucessfully.

À



 






 

These software metrics will be taken care by SQA team
Ex:rate of deffect efficiency

J











t is a software testing related technique which is used for writing test cases.it will break the range
into some wqual partitions.the main purpose of this tecnique is 
1) To reduce the no. of test cases to a necessary minimun.
2) To select the right test cases to cover all the senarios.













Test plan is a document which contains scope,risk analysis.
for every sucess there should be some plan,like that for geting some quality product proper test plan
should be there.

The test plan Contents are:
1) introduction
a) Overview
b) Achronyms
2) Risk Analysis
3) Test items
4) Features and funtions to be test
5) Features and funtions not to be test
6) Test statergy
7) test environment
8) system test shedule
9) test delivarables
10) Resources
11) re-sumptiom and suspension criteria
12) staff and training

£




 



equirement specifications and User interface documents(sreen shots of application)






! 
 

"

 
"
Mainly to check the look and feel,ease of use,gui(colours,fonts,allignment),help manuals and
complete end to end navigation.



#
 
 
 

Here in this testing mainly we will check the functionality of the application whether its meet the
customer requirements are not.
Ex:1+1 =2.

c

$%&




V model

À
"

'
(
'

A:Verification and Validation Model.

)



 

 
*

+ 
t will be specified by the customer what is his acceptance criteria.Ex:if so and so functionality has
worked enough for me.

J


,

&-



Loc (lines of code) it will depend on the any company standards they are following.







!

by using Bug tracking tool like Bugzilla,test director again it may depends on company,some
companies they may use own tool.

.
"



/ 

 


 1) SRS
2) Planning
3) Test senario design
4) Test case design
5) Execution
6) Bug Reporting
7) maintainance