Test Execution
Test Execution is the phase of the testing lifecycle where designed test cases are run, actual results are compared with expected results, and defects are identified and reported.
Test execution answers: “Does the application behave as expected?”
1. Definition
Test Execution is the phase of the testing lifecycle where designed test cases are run, actual results are compared with expected results, and defects are identified and reported.
2. Purpose of Test Execution
- Validate implemented functionality against requirements
- Identify defects and quality risks
- Provide evidence of testing
- Support release decisions
3. Preconditions for Test Execution
Before execution starts:
- Approved test cases are available
- Test environment is ready
- Build is deployed and stable
- Test data is prepared
- Entry criteria are met
4. Test Execution Activities (Step-by-Step)
4.1 Execute Test Cases
- Follow test steps precisely
- Use defined test data
- Avoid assumptions
4.2 Record Results
- Mark test cases as Pass / Fail / Blocked
- Capture actual results clearly
4.3 Log Defects
- Raise defects for failed cases
- Attach screenshots or evidence
- Assign severity and priority
4.4 Re-Test Fixes
- Verify defect fixes in new builds
- Update defect status
4.5 Regression Testing
- Re-run impacted test cases
- Ensure fixes didn’t break existing functionality
5. Types of Test Execution (Manual)
- Functional test execution
- Smoke test execution
- Sanity test execution
- Regression test execution
- Exploratory test execution
- UAT support execution
6. Manual Tester’s Responsibilities
- Execute test cases accurately
- Maintain execution discipline
- Log high-quality defects
- Update execution status timely
- Communicate blockers and risks
7. Test Execution vs Test Design
| Aspect | Test Execution | Test Design |
|---|---|---|
| Focus | Validation | Preparation |
| Output | Pass/Fail, defects | Test cases |
| Timing | After build | Before execution |
8. Test Execution Deliverables
- Executed test cases
- Defect reports
- Test execution report / daily status
- Updated RTM
9. Common Issues During Test Execution
- Environment instability
- Incomplete test data
- Frequent build changes
- Time pressure
- Blocked test cases
10. Best Practices
- Execute tests systematically
- Prioritize high-risk areas
- Keep evidence for failures
- Communicate issues early
- Follow exit criteria
11. Interview-Ready Answers
Short answer:
Test execution is the process of running test cases and comparing actual results with expected results.
Detailed answer:
Test execution involves executing test cases in a prepared environment, logging defects for failures, re-testing fixes, and reporting testing progress.
12. Key Takeaway
Test Execution converts planning and design into real quality validation, revealing the true state of the product.