Review:

1. For its Completeness
2. For its Correctness
3. For its Consistency
4. For its Uniqueness

Test Case Review checklist:

1. Do the integration test cases accurately implement the integration test plan?
2. Are all materials in the proper physical format?
3. Does each integration test case include a complete description of the expected input and output or result?
4. Have all testing dependencies been addressed (driver function, hardware, etc.)?
5. Are the integration test cases unambiguous?
6. Are all data set definitions and set-up requirements complete and accurate?
7. Have all inter-case dependencies been identified and described?
8. Is each condition tested once and only once?
9. Are all test entrance and exit criteria observed?
10. Are the integration test cases designed to show the reaction to failure and not merely the absence of failure?
11. Are the integration test cases designed to show omissions and extensions?
12. Are the integration test cases correct?
13. Are the integration test cases realistic?
14. Are internal Configuration Management set up, directories established, and case data and tools loaded?
15. Are operator instructions and status indicators complete, accurate, and simple?
16. Have all testing execution procedures been defined and documented?
17. Have all integration test case standards been followed?
18. Has the entire testing environment been documented?
19. Are the integration test cases documented so as to be 100% reproducible?
20. Documentation has to be verified whether it is clear and understandable for the typical audience of the documentation

Approval:

1. By Team Leader
2. By Test Manager
3. By Project Manager
4. By Client

Test Execution

Inputs:

1. Executable Code
2. Design Document
3. Unit Test cases
4. Unit Test Report
5. Code Walkthrough Report
6. Approval by Project/Test Manager
7. Integration Test Cases
8. Integration Test Case Report
9. Integration Test Plan

Process:

1. Perform random unit testing
2. Random test-passes then start Integration testing phase, fails return back to the developer
3. Perform Integration testing as detailed in the test plan using the test cases and procedures
4. Corresponding stub or driver program will be identified and executed for each Test Case.
5. Document the test cases with actual results
6. Track the Integration Test report in Test Repository.

Output:

· Test Case Report

Test Evaluation

Inputs:

1. Integration Test Case Report
2. Defect Classification
3. Integration test plan

Process:

1. Analyze the test results to determine that software correctly implements the requirements
2. Identify the Test Cases that are failed and trace out the exact scenario and description of the failure that resulted in the failure of the test case.
3. Classify the defects as per defect classification guidelines
4. Are the interfaces tested as specified in the integration test plan?

Output:

· Issue Log

Test Reporting

Below steps are to be followed for each execution of test process

Input:

1. Test case Report
2. Defect Classification Report
3. Issue log

Test Report Process:

· Document the bug description for each failed Test Case in the Test Report

· Document the Summary Report after completing the test process

Output:

1. Test Case Report
2. Test Report
3. Test Summary Report

Test Report Description:

1. Report ID
2. Report Title
3. ProjectName & Version
4. Environment
5. TestCase ID
6. ModuleName
7. Date of testing
8. Tested By

Iteration

1. Bug Description
2. Defect type classification
3. Priority
4. Status
5. Tester comments
6. Developer comments

Test Summary Report Description:

1. Report ID
2. Report Title
3. PorjectName & Version
4. Author
5. Summary of Defects found with severity
6. Summary of test cases executed with priority
7. Number of resources worked
8. Start Date
9. End Date
10. Time Period
    

7.3

RELATED POST

DESIGNING TEST CASES