Test prioritization in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is test prioritization in software testing?

Test prioritization is the process of deciding the order in which test cases should be executed to find defects faster and use resources efficiently.

beginner

Why is test prioritization important?

It helps testers find critical bugs early, saves time, and makes the testing process more efficient by focusing on the most important tests first.

intermediate

Name two common criteria used for test prioritization.

1. Risk of failure or impact of a feature.<br>2. Frequency of use or critical business functions.

intermediate

How does test prioritization relate to regression testing?

In regression testing, prioritization helps run the most important tests first to quickly check if recent changes broke key features.

beginner

Give an example of a simple way to prioritize tests.

Assign high priority to tests covering new or changed features, medium priority to important but unchanged features, and low priority to less critical areas.

What is the main goal of test prioritization?

A To find defects faster and use testing time wisely

B To run all tests in alphabetical order

C To skip tests that are easy

D To test only the user interface

Test prioritization aims to find defects faster and make good use of limited testing time by running important tests first.

Which factor is commonly used to prioritize tests?

A The color of the test case document

B The risk or impact of the feature being tested

C The number of testers available

D The size of the software company

Tests are often prioritized based on the risk or impact of the feature to catch serious bugs early.

In regression testing, why prioritize tests?

A To test only the database

B To test only new features

C To avoid testing old features

D To quickly check if recent changes broke important parts

Prioritizing regression tests helps quickly find if recent code changes caused problems in key areas.

Which of these is NOT a good reason to prioritize a test?

A The test is the shortest to run

B The feature was recently changed

C The feature is critical to users

D The feature has a history of bugs

Test length alone is not a good reason to prioritize; importance and risk matter more.

What happens if you do NOT prioritize tests?

A You find bugs faster

B All tests run in parallel

C Testing may waste time on less important areas

D Tests become automated automatically

Without prioritization, testing might spend too much time on less important tests and miss critical bugs early.

Explain what test prioritization is and why it matters in software testing.

Think about how you would decide which tasks to do first when you have limited time.

Describe common criteria used to decide which tests to run first.

Consider what makes a feature important or risky.