3.1.5 - Test Execution

Interactive Audio Lesson

Listen to a student-teacher conversation explaining the topic in a relatable way.

Introduction to Test Execution

Unlock Audio Lesson

Signup and Enroll to the course for listening the Audio Lesson

Teacher
Teacher

Today, we’re going to discuss the Test Execution phase of the Software Testing Life Cycle. Can anyone tell me why this phase is crucial?

Student 1
Student 1

It’s where we actually run the test cases, right?

Teacher
Teacher

Exactly! Executing test cases helps us find defects in the software. What do we do if we find issues?

Student 2
Student 2

We log them in a defect tracking tool, like JIRA!

Teacher
Teacher

Correct! Logging defects is essential, as it assists the development team in addressing the issues. Remember, we want to compare actual results to expected outcomes. Why do we do this?

Student 3
Student 3

To ensure the software meets the requirements?

Teacher
Teacher

Yes! This is foundational to quality assurance. Let’s recap: executing means running tests, finding means logging issues, and comparing helps confirm requirements.

Deliverables in Test Execution

Unlock Audio Lesson

Signup and Enroll to the course for listening the Audio Lesson

Teacher
Teacher

Now, let’s talk about the deliverables from the Test Execution phase. What do you think we produce?

Student 4
Student 4

The Test Execution Report!

Teacher
Teacher

That’s right! It summarizes the results of the executed test cases. What else do we document?

Student 1
Student 1

We also create a Defect Report that lists all the issues found.

Teacher
Teacher

Correct! And we keep the Requirements Traceability Matrix updated to reflect our current coverage status. Why do you think this is important?

Student 2
Student 2

It shows the link between requirements and testing, helping to ensure nothing is missed!

Teacher
Teacher

Excellent point! Connecting everything helps maintain a clear overview of what has been tested against the requirements.

Entry and Exit Criteria for Test Execution

Unlock Audio Lesson

Signup and Enroll to the course for listening the Audio Lesson

Teacher
Teacher

Let’s dive into the entry and exit criteria for Test Execution. What does entry criteria mean?

Student 3
Student 3

It’s the conditions we need to meet before starting Test Execution.

Teacher
Teacher

Exactly! What are some examples of entry criteria?

Student 4
Student 4

Test cases and test data must be ready, and the environment has to be operational.

Teacher
Teacher

Well done! Now, what about exit criteria? What do we look for before completing Test Execution?

Student 1
Student 1

All critical test cases must be executed, and any major bugs must be fixed or deferred.

Teacher
Teacher

Exactly! Having clear entry and exit criteria ensures a thorough and structured approach to testing.

Retesting and Regression Testing

Unlock Audio Lesson

Signup and Enroll to the course for listening the Audio Lesson

Teacher
Teacher

Following defect logging, what do we commonly perform?

Student 2
Student 2

We retest the areas where bugs were found to make sure they are fixed.

Teacher
Teacher

Exactly! And what is regression testing?

Student 3
Student 3

It’s testing the entire system again to ensure that new changes haven’t caused any issues.

Teacher
Teacher

Spot on! Regression testing is vital to maintain software stability. Remember—Testing is iterative!

Introduction & Overview

Read a summary of the section's main ideas. Choose from Basic, Medium, or Detailed.

Quick Overview

Test Execution is a critical phase in the Software Testing Life Cycle, focused on executing test cases and reporting any defects found.

Standard

The Test Execution phase involves executing manual or automated test cases, recording results, and logging defects. It plays a vital role in identifying software issues and ensures that the final product meets quality standards before release.

Detailed

Test Execution

The Test Execution phase is a pivotal part of the Software Testing Life Cycle (STLC) that focuses on executing the prepared test cases and documenting the outcomes. This step is essential for determining if the software functions as expected and meets the defined requirements.

Key Objectives

  • Execute test cases: Both manual and automated test cases are executed during this phase.
  • Report defects: Any discrepancies between expected and actual results must be logged accurately.

Core Activities

  1. Execute Test Cases: Testers run the prepared test cases using the defined test environment and data.
  2. Record Results: The actual outcomes of each test case are compared against the expected results.
  3. Log Defects: If discrepancies arise, defects are recorded using tools like JIRA.
  4. Retest After Fixes: Once defects are addressed, testing teams must retest the affected areas to ensure fixes were successful.

Deliverables

  • Test Execution Report: Summarizes the execution results, detailing passed and failed test cases.
  • Defect Report: Provides insights into discovered defects along with tracker updates.
  • Updated Requirements Traceability Matrix (RTM): Reflects the current status of test coverage and defect resolution.

Entry and Exit Criteria

  • Entry Criteria: Ensuring test cases and test data are ready, and the test environment is operational.
  • Exit Criteria: All critical test cases must be executed, and critical bugs addressed or deferred with appropriate approvals.

Overall, the effectiveness of the Test Execution phase significantly influences software quality, delivering software solutions that are robust and functional.

Audio Book

Dive deep into the subject with an immersive audiobook experience.

Objective of Test Execution

Unlock Audio Book

Signup and Enroll to the course for listening the Audio Book

Objective: Execute test cases and report any defects found.

Detailed Explanation

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.

Examples & Analogies

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 Involved in Test Execution

Unlock Audio Book

Signup and Enroll to the course for listening the Audio Book

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

Detailed Explanation

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.

Examples & Analogies

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 of Test Execution

Unlock Audio Book

Signup and Enroll to the course for listening the Audio Book

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

Detailed Explanation

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.

Examples & Analogies

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 and Exit Criteria for Test Execution

Unlock Audio Book

Signup and Enroll to the course for listening the Audio Book

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

Detailed Explanation

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.

Examples & Analogies

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).

Definitions & Key Concepts

Learn essential terms and foundational ideas that form the basis of the topic.

Key Concepts

  • Test Execution: The phase where test cases are executed.

  • Defect Reporting: Documenting issues discovered during testing.

  • RTM: Tool for tracking test coverage against requirements.

  • Entry and Exit Criteria: Conditions to begin and end each testing phase.

  • Retesting and Regression: Verifying fixes and maintaining overall quality.

Examples & Real-Life Applications

See how the concepts apply in real-world scenarios to understand their practical implications.

Examples

  • When a test case fails, a defect report is created in JIRA to document the issue.

  • Before moving to the Test Closure phase, all critical bugs must either be fixed or deferred.

Memory Aids

Use mnemonics, acronyms, or visual cues to help remember key information more easily.

🎵 Rhymes Time

  • Test cases we do run, to find bugs is the fun, logging issues each time, ensures quality will climb.

📖 Fascinating Stories

  • Imagine a chef testing a recipe. Each ingredient is a test case, when it tastes off, they log what needs fixing and try again to perfect the meal.

🧠 Other Memory Gems

  • Remember: E.R.A. for Test Execution - Execute, Report, Assess.

🎯 Super Acronyms

T.E.S.T. - Test Execution, Summarize results, Track defects.

Flash Cards

Review key concepts with flashcards.

Glossary of Terms

Review the Definitions for terms.

  • Term: Test Execution

    Definition:

    The phase in the STLC where test cases are executed, and results are recorded.

  • Term: Defect Report

    Definition:

    Documentation of defects found during test execution, detailing issues for resolution.

  • Term: Requirements Traceability Matrix (RTM)

    Definition:

    A document that captures the relationship between requirements and test cases.

  • Term: Entry Criteria

    Definition:

    Conditions that must be met before a test phase can start.

  • Term: Exit Criteria

    Definition:

    Conditions that must be fulfilled before concluding a test phase.

  • Term: Retesting

    Definition:

    The testing conducted on fixed defects to ensure their resolution.

  • Term: Regression Testing

    Definition:

    Testing to confirm that recent changes haven’t adversely affected existing functionality.