Tuesday, 18 October 2011

Test Cases Design:

1.     Test Cases Design:

What is a test case?
Test case is a description of what to be tested, what data to be given and what actions to be done to check the actual result against the expected result.

What are the items of test case?

  1. Test Case Number
  2. Pre-Condition
  3. Description
  4. Expected Result
  5. Actual Result
  6. Status (Pass/Fail)
  7. Remarks.
Test Case Template

TC ID
Pre-Condition

Description

Expected Result

Actual Result

Status
Remarks
Unique Test Case number 
Condition to satisfied 
  1. What to be tested
  2. what data to provided
  3. what action to be done
As pear FSR
System response
Pass or
Fail
If any
Yahoo-001 
Yahoo web page should displayed
1.      Check inbox is displayed
2.      User ID/PW
3.      Click on Submit
System should mail box
System response




Types of Test Cases
Type
Source
1. Requirement Based
Specifications
2. Design based
Logical system
3. Code based
Code
4. Extracted
Existing files or test cases
5. Extreme
Limits and boundary conditions

Can this test cases reusable?
      Test cases developed for functionality testing and can be reusable for
  • Integration
  • System                  
  • Regression
  • Performance             

What are the characteristics of good test case?
A good test case should have the following:
  • TC should start with “what you are testing”.
  • TC should be independent.
  • TC should not contain “If” statements.
  • TC should be uniform. (Convention should be followed same across the Project     Eg. <Action Buttons> , Links
The following issues should be considered while writing the test cases
  • All the TC’s should be traceable.
  • There should not be any duplicate test cases.
  • Out dated test cases should be cleared off.
  • All the test cases should be executable.
 Test case Guidelines
  • Developed to verify that specific requirements or design are satisfied
  • Each component must be tested with at least two test cases:  Positive and Negative
  • Real data should be used to reality test the modules after successful test data is used

3.5 Test Case Review:
  1. Peer to peer Reviews
  2. Team Lead Review
  3. Team Manager Review

Review Process

















3.6 Test Case Execution:
  • Test execution is completion of testing activities, which involves executing the planned test cases and conducting of the tests.
  • Test execution phase broadly involves execution and reporting.
  • Execution and execution results plays a vital role in the testing.
Test execution consists of following activities to be performed
1.     Creation of test setup or Test bed
2.     Execution of test cases on the setup
3.     Test Methodology used
4.     Collection of Metrics
5.     Defect Tracking and Reporting
6.     Regression Testing       

The following activities should be taken care:
1.     Number of test cases executed.
2.     Number of defects found
3.     Screen shoots of failure executions should be taken in   word document.
4.     Time taken to execute.
5.     Time wasted due to the unavailability of the system.

Test Case Execution Process:

Take the Test Case document  

 


Check the availability of application 

 


Implement the Test Cases

 



Raise the Defects 

 
                                                                              





 




   







INPUT
 




PROCESS
 


 

No comments: