CH 5 Test Management quiz

Risk-based testing

A testing approach that uses stakeholder knowledge and risk analysis to determine testing priorities and levels.

Test pyramid

A model that organizes tests into unit tests, integration tests, and end-to-end tests.

Unit tests

Tests at the lowest level of the test pyramid that verify individual components.

Integration tests

Tests that verify interactions between components.

End-to-end tests

Tests that validate complete user workflows across the entire system.

Project risk

Risk focused on the capability to deliver the product.

Configuration management

The process of establishing and maintaining the integrity of components, systems, testware, and their relationships throughout the lifecycle.

Exit criteria

Conditions used to determine when a test activity has been completed or should stop; in Agile, Definition of Done.

Risk-based prioritization

A strategy where tests with the highest likelihood and impact of failure are executed first.

Requirements-based prioritization

A strategy where tests linked to the highest-priority stakeholder requirements are executed first.

Additional coverage prioritization

A strategy that prioritizes tests providing the greatest additional coverage after initial high-coverage tests.

Coverage-based prioritization

A strategy where tests providing the highest amount of coverage are run first.

Defect management

The process of recognizing, investigating, recording, classifying, and resolving defects.

Configuration item

An item managed by configuration management.

Complex configuration item

A collection of configuration items with relationships and versions, such as a test environment.

Baseline change

A record of changes made to a baseline, including version information and timing.

Baseline

A configuration item approved for testing that can only be changed through formal change control.

Configuration management system

A system that allows testers to identify the exact code and documentation versions being tested.

Product risk

Risk focused on the quality of the product.

Expert method

An estimation technique that relies on the experience of knowledgeable individuals.

Failure

An unplanned event where actual results differ from expected results and requires investigation.

Extrapolation

An estimation technique that uses data from previous or similar projects.

Level of risk

The probability of a risk occurring multiplied by its impact.

Test suite

A collection of test cases and test procedures grouped by specific criteria.

Mitigating action

An action intended to reduce either the likelihood or impact of a risk.

Quadrant Q1

Technology-facing tests that support the team, such as component, integration, and API tests.

Quadrant Q2

Business-facing tests that support the team, such as functional tests and user story tests.

Quadrant Q3

Business-facing tests that critique the product, such as exploratory and usability testing.

Quadrant Q4

Technology-facing tests that critique the product, such as security and performance testing.

Risk

A factor that could result in future negative consequences.

Test progress report

A report produced during testing to update stakeholders on testing activities and status.

Test completion report

A report produced after testing is finished to summarize testing activities and results.

Business-facing

Testing quadrants Q2 and Q3.

Support the team

Testing quadrants Q1 and Q2.

Critique the product

Testing quadrants Q3 and Q4.

Technology-facing

Testing quadrants Q1 and Q4.

Estimate based on ratios

A data-driven estimation approach using metrics collected from the current project.

Three-point estimation

An expert-based estimation technique using optimistic, likely, and pessimistic estimates.

Entry criteria

Conditions that must be met before a test activity can begin; in Agile, Definition of Ready.

Smoke tests

High-level tests that verify critical functionality and system stability.

User acceptance testing

Testing performed by users to determine whether the system meets business needs.

Component tests

Tests of individual software components.

API testing

Testing of application programming interfaces.

Functional tests

Tests that verify required system functionality.

Non-functional tests

Tests that evaluate performance, security, reliability, and other quality attributes.

User experience prototypes

Prototype evaluations used to assess user interactions and experience.

User story tests

Tests derived from user stories and acceptance criteria.

Usability testing

Testing focused on ease of use and user satisfaction.

Examples

Concrete examples used to define and validate expected behavior.

Security testing

Testing designed to identify vulnerabilities and verify security controls.

Exploratory testing

Testing that combines learning, test design, and execution simultaneously.

Simulations

Tests that model real-world conditions or environments.

Component integration tests

Tests that verify interactions between integrated components.