Skip to main content

Risk-Based Testing

  • Risk-based testing focuses on prioritizing testing efforts based on the likelihood and impact of potential defects. It ensures that the most critical areas of the system are tested first.
  • Identifying potential risks that could affect the quality of the system, such as areas with high complexity, frequently changing code, or previous defect history.

Test Progress Monitoring and Reporting​

  • Monitoring and reporting are essential to track the status of testing activities and communicate the results to stakeholders.

Key Concepts

  • Test Progress Metrics:

    • Test Case Execution Status: Number of test cases planned, executed, passed, failed, or blocked.

    • Defect Metrics: The number of defects reported, fixed, and still open.

    • Test Coverage: The percentage of requirements or code covered by tests.

  • Test Reports:

    • Daily / Weekly Test Reports: Provide regular updates on test execution and defect status.

    • Test Summary Report: A high-level report summarizing the overall testing activities, results, and outcomes after testing is completed.

Configuration Management​

  • Configuration management in the context of testing refers to managing the versions and states of test artifacts, such as test cases, test scripts, and test environments. This ensures that changes to the test artifacts are tracked and controlled.

Key Concepts

  • Version Control: Managing different versions of test cases and scripts to ensure that the right version is used for each test cycle.

  • Test Environment Configuration: Managing the hardware, software, and network configurations used in the test environment to ensure consistency across different test cycles.

Defect Management​

  • Defect management refers to the process of identifying, logging, tracking, and resolving defects found during testing.

Key Concepts

  • Defect Life Cycle: The process a defect follows from its discovery to its resolution. The typical stages include:

    • New: The defect is logged and awaiting analysis.

    • Assigned: The defect is assigned to a developer for fixing.

    • Fixed: The developer has resolved the defect.

    • Retested: The defect is retested by the tester to confirm the fix.

    • Closed: The defect is verified and closed, or reopened if the issue persists.

  • Defect Severity: Indicates the impact of the defect on the system. ie: Critical, Major and Minor.

  • Defect Priority: Represents the urgency with which the defect needs to be fixed. ie: High, Medium and Low.

Incident Management​

  • Incident management involves managing any unexpected events or deviations from expected behavior observed during testing. Incidents are logged and tracked until resolved.

Key Concepts

  • Incident Reporting: Documenting incidents such as defects, anomalies, or environmental issues that occur during testing.

  • Incident Tracking: Monitoring the status of incidents to ensure they are addressed and resolved in a timely manner.

Test Automation Management​

  • Test automation management involves planning, implementing, and maintaining automated test scripts to support the testing process. Automation is often used for regression testing or repetitive tasks to increase efficiency.

Key Concepts

  • Automation Strategy: Defining which tests to automate, which tools to use, and how to maintain automated tests.

  • Automated Test Scripts: Scripts written to execute test cases automatically. Maintenance of Automation: Updating automated scripts as the software changes to ensure that tests remain valid.

Test Metrics and Measurement​

  • Test metrics provide quantitative measures to assess the effectiveness and efficiency of the testing process.

Key Concepts

  • Test Coverage: The extent to which the software has been tested, measured as a percentage of requirements or code executed by tests.

  • Defect Density: The number of defects found per unit of software size. ie: Defects Per Thousand Lines of Code.

  • Test Execution Metrics: Number of test cases executed, passed, failed, or blocked.

  • Defect Metrics: Time taken to resolve defects, defect severity distribution, and defect detection rate.

  • Productivity Metrics: Measures the efficiency of the testing team, such as test cases executed per person-hour.

Test Policy and Strategy​

  • A Test Policy is a high-level document that outlines the organization's overall approach to testing, including goals, principles, and objectives. A Test Strategy provides more detailed guidance on how testing will be conducted for specific projects or phases.

Key Concepts

  • Test Policy: Describes the long-term vision, objectives, and goals for testing within the organization.

  • Test Strategy: Defines the general approach to testing for a specific project, including the testing levels, types, tools, and techniques to be used.

Test Organization​

  • Test organization deals with the structure of the testing team and their responsibilities within the project.

Key Concepts

  • Test Manager: Responsible for planning, monitoring, and controlling the testing activities.

  • Test Lead: Guides the day-to-day execution of testing, reporting to the test manager.

  • Test Analysts and Testers: Responsible for designing, executing, and reporting test cases.

  • Independent Testing Team: A team of testers who are separate from the development team, ensuring objective and unbiased testing.

Module Review​

Click to start the definition to term matching quiz
Drag the defintion to the correct term.
Test type item not available at this time.
Click to start the multiple choice quiz
Choose from the listed options below.
Test type item not available at this time.