3.1.5. Test Execution

Objective: Execute test cases and report any defects found.

The main objective of the Test Execution phase is to run the test cases that have been developed in the previous steps. This involves identifying whether the software behaves as expected. During this phase, testers will also document any defects they find, ensuring that issues are recorded for further analysis and resolution.

Think of this phase like a rehearsal for a play. The actors (testers) perform the script (test cases) to ensure everything runs smoothly. If they encounter any wrong lines or missed cues (defects), they need to note those down so they can be fixed before the final show (the software release).

Activities: ● Execute manual/automated tests ● Record actual results and compare with expected outcomes ● Log defects in tools like JIRA ● Retest after defect fixes

In the Test Execution phase, testers perform several key activities. First, they execute both manual and automated tests according to the test cases prepared earlier. After running the tests, they compare the actual outcomes with expected results to check for discrepancies. Any defects found are documented in issue-tracking tools such as JIRA for tracking and management. Additionally, once defects are fixed by the development team, the testers will re-run the tests to verify that the issues have been resolved.

Imagine a chef following a recipe (test case) to prepare a dish. As they cook (executing tests), they taste the food (comparing actual results to expected outcomes). If something doesn’t taste right (a defect), they take notes for adjustments. After the corrections are made (defect fixes), the chef would taste the food again to ensure it's perfect before serving it (retesting).

Deliverables: ● Test Execution Report ● Defect Report & Bug Tracker Updates ● Updated RTM

At the end of the Test Execution phase, several important documents and records are produced. The Test Execution Report summarizes the outcomes of the test cases run, noting which passed and which failed. A Defect Report details the defects found during testing and is updated in the bug tracking system for visibility and tracking. Additionally, the Requirements Traceability Matrix (RTM) is updated to reflect the testing outcomes, ensuring that testers and stakeholders have clear visibility into what has been tested and what remains.

Continuing with the chef analogy, after finishing a meal, the chef might write down a summary of how it went (Test Execution Report), list any problems encountered (Defect Report), and update their recipe book with notes about what worked and what didn’t (Updated RTM). This documentation helps future cooking sessions go more smoothly.

Entry Criteria: ● Test cases and test data are ready ● Test environment is up and running Exit Criteria: ● All test cases executed ● All critical bugs are fixed or deferred with approval

Before starting Test Execution, certain conditions must be satisfied, known as entry criteria. This includes ensuring that all test cases are prepared and the necessary test data and environment are functional. Once the test execution is completed, exit criteria are assessed to determine if the phase can be closed. This means all test cases should have been executed, and any critical bugs must either be resolved or adequately deferred with approval from stakeholders.

Think of entry criteria as the checklist a pilot completes before takeoff. They must ensure all systems are operational and ready for flight. Once they land (exit criteria), they verify that the journey is complete, ensuring that all planned miles have been flown (test cases executed), and that any issues during the flight are acknowledged and addressed (bugs fixed or deferred).

--