Introduction
Test Execution is the phase where testers execute prepared test cases to validate the application functionality. In real-time projects, this phase ensures that the system works as expected before release.
It is one of the most critical stages in the software testing lifecycle.
What is Test Execution?
Test Execution is the process of running test cases manually or automatically to identify defects. The goal is to compare expected results with actual results.
- Validate functionality
- Identify defects
- Ensure requirement coverage
- Update execution status
Pre-Execution Activities
- Test cases must be approved
- Test environment should be ready
- Test data should be prepared
- Build should be stable
Step-by-Step Test Execution Process
- Receive Build: Confirm build version.
- Smoke Testing: Validate basic functionality.
- Execute Test Cases: Follow test steps.
- Capture Results: Record actual results.
- Log Defects: Report mismatches.
- Retest: Verify fixed issues.
- Regression Testing: Ensure stability.
Test Case Status Types
- Pass
- Fail
- Blocked
- Not Executed
Execution Reporting
- Daily execution status report
- Defect summary report
- Test coverage percentage
- Open vs Closed defects count
Execution reports help stakeholders understand product quality before release.
Interview Questions
What is Test Execution in manual testing?
Test Execution is the process of running test cases to verify application functionality and identify defects.
What happens after test execution?
Defects are reported, retesting and regression testing are performed.
What is smoke testing during execution?
Smoke testing validates critical functionalities before detailed testing begins.
Frequently Asked Questions
Can execution start without environment setup?
No, environment setup is mandatory before test execution.
Why is regression testing needed after execution?
To ensure new changes have not affected existing functionality.