Wednesday, 5 November 2014

Test Execution



Once the preparation of Test Case Development and Test Environment setup is completed then test execution phase can be kicked off. In this phase testing team start executing test cases based on prepared test planning & prepared test cases in the prior step.
Once the test case is passed then same can be marked as Passed. If any test case is failed then corresponding defect can be reported to developer team via bug tracking system & bug can be linked for corresponding test case for further analysis. Ideally every failed test case should be associated with at least single bug. Using this linking we can get the failed test case with bug associated with it. Once the bug fixed by development team then same test case can be executed based on your test planning.
If any of the test cases are blocked due to any defect then such test cases can be marked as Blocked, so we can get the report based on how many test cases passed, failed, blocked or not run etc. Once the defects are fixed, same Failed or Blocked test cases can be executed again to retest the functionality.
Entry Criteria
Activities
Deliverable
1.    Test Plan or Test strategy document.

2.    Test cases.

3.    Test data.
1.      Based on test planning execute the test cases.

2.      Mark status of test cases like Passed, Failed, Blocked, Not Run etc.


3.      Assign Bug Id for all Failed and Blocked test cases.

4.      Do Retesting once the defects are fixed.


5.    Track the defects to closure.
1.      Test case execution report.

2.    Defect report.

0 comments:

Post a Comment