GeekInterview.com
  I am new, Sign me up!
 
GeekInterview.com  >  Interview Questions  >  Testing  >  Test Cases
Go To First  |  Previous Question  |  Next Question 
 Test Cases  |  Question 254 of 258    Print  
Test Case Review
Suppose your colleague has written test cases for a functionality and you are reviewing those test cases, how will you conclude that the test cases were correct?


  
Total Answers and Comments: 7 Last Update: August 26, 2009     Asked by: vk1978 
  
 Sponsored Links

 
 Best Rated Answer
Submitted by: shakilag
 
Things to verify while carrying out test case review:

1) All the requirements mentioned in FRS are covered.

2) All negative scenario tests are covered.

3) Boundary Value Conditions are covered. i.e Tests covering lower/upper bounds are covered.

4) Data Validity tests are covered.

5) All the GUI related test cases (if mentioned in FRS) are covered.

Above answer was rated as good by the following members:
venakks, ram4u, ahamedjameel, tracysha, riddle
March 28, 2009 13:46:18   #1  
phani_k07 Member Since: January 2007   Contribution: 6    

RE: Test Case Review

We will review the test case functionality as per functional document. If we find any deviations from the functional specs we will not sign off the test cases and we comment the reason for not signing off the test case.

 
Is this answer useful? Yes | NoAnswer is useful 2   Answer is not useful 0Overall Rating: +2    
May 14, 2009 08:18:31   #2  
shraddhacold Member Since: June 2008   Contribution: 2    

RE: Test Case Review

We will check out the testcases have covered all the application requirements. From the requirement documents we will match the test case are wriiten taking in to requirement specifications


 
Is this answer useful? Yes | No
May 14, 2009 20:19:41   #3  
mk2780 Member Since: November 2005   Contribution: 1    

RE: Test Case Review
You need to match the requirements and see that those have been analyzed and all scenarios have been included. Negative test cases have been included. Also the template is complete all sections of it is filled up as relevant. the following test case attributes need to be considered ..
A test case should stand by itself it should be examplary.


 
Is this answer useful? Yes | No
June 23, 2009 02:15:23   #4  
shakilag Member Since: June 2009   Contribution: 10    

RE: Test Case Review
Things to verify while carrying out test case review:

1) All the requirements mentioned in FRS are covered.

2) All negative scenario tests are covered.

3) Boundary Value Conditions are covered. i.e Tests covering lower/upper bounds are covered.

4) Data Validity tests are covered.

5) All the GUI related test cases (if mentioned in FRS) are covered.

 
Is this answer useful? Yes | NoAnswer is useful 3   Answer is not useful 0Overall Rating: +3    
July 10, 2009 03:19:52   #5  
saravanan123 Member Since: July 2009   Contribution: 163    

RE: Test Case Review
Whether we can check by referring with SRS and check whether we make the testcase for all the main functionalities covered or not.
 
Is this answer useful? Yes | No
August 12, 2009 02:19:26   #6  
mathan_vel Member Since: December 2007   Contribution: 422    

RE: Test Case Review
by verified with SRS and functional document. if there is any variance on the Test Steps and expected results the concern Test case should be approved. Those Test case should be marked and highlighted and have discussed in meeting.
 
Is this answer useful? Yes | No
August 25, 2009 09:04:14   #7  
ashishks Member Since: December 2008   Contribution: 73    

RE: Test Case Review
I will consider the following thing while reviewing test cases:

1. Test cases are written exactly by following requirements.
2. There must be at least one test case for the functionalities described in the requirements.
3. There should not be any dupliacte test case.
4. Test cases should be best fit to its bread.
5. Test cases should be neither too simple nor too complex.
6. Test data should be clear and should be correct.
7. Test case should be so clear that anyone should be able to understand properly.
8. Test cases should match for its type i.e. usability test cases should not be written while writing functional test cases.

If there is any descripency found in test cases then we should mark them and clearly mention the reason for incorrectness and alternatives to correct them.

 
Is this answer useful? Yes | NoAnswer is useful 1   Answer is not useful 0Overall Rating: +1    


 
Go To Top


 Sponsored Links

 
About Us -  Privacy Policy -  Terms and Conditions -  Contact -  Ask Question -  Propose Category -  Site Updates 

Copyright © 2005 - 2009 GeekInterview.com. All Rights Reserved

Page copy protected against web site content infringement by Copyscape