Hi,

1.Before start testing any application, try to get minimum 
awareness of the domain. 
2. Try to check whether all test cases are executed in the 
module given to u.
3. Try to look for Usability testing along with functional 
testing.
4.If it is web application, try to concentrate on all links 
and page navigations...Make sure that you have covered all 
areas of application in the given module to u.  It is 
possible only when u know the functionality clearly...

Check if u met the exit criteria or not. If you met exit
criteria then u can make sure your testing is completed.

@ krishna 
thanks ur reply 
i don't have full length documents, i have only whats the
functions in module, 'how they work' don't specify in that
simple docs
this is situation what i can do?

@Gest

Hi,

Please let me know on which domain u r working and what are 
all the basic functionalities of ur application, so that i 
will help u in sending test scenarios and finding out the 
functional points...if you have screen shots of ur 
application send it to pskrishnamohan@sgtechnologies-in.com

Through RTM we come to know whether we tested the 
application fully
RTM is a doc through which we match the test cases and test 
requirements.

Hi Janet..
Actually testing will be stopped based on the Acceptance 
criteria i.e. when to stop testing by feeling that we have 
performed enough testing..but there is no particular 
criteria to say that in every company for every 
project..so..you have to perform re and regression testing 
each time you get the bugs and bugs fixed from development 
department..make sure that according to RTM all test cases 
are passed and all bugs that you have raised are 
closed...that itself defines the completion of 
testing...but usability testing gets added to 
that..usability testing in the sense user-
friendliness..that varies from every testrer's perception. 
that is y i asked u to get minimum awareness of domain so 
that you will know how users can satisfy with the 
application..I think you got my words..if any doubts you 
can ask me regarding work.

This can be difficult to determine. Many modern software 
applications are so complex, and run in such an 
interdependent environment, that complete testing can never 
be done. Common factors in deciding when to stop are: 
• Deadlines (release deadlines, testing deadlines, etc.) 
• Test cases completed with certain percentage passed 
• Test budget depleted 
• Coverage of code/functionality/requirements reaches a 
specified point 
• Bug rate falls below a certain level 
• Beta or alpha testing period ends