Risk-Based Regression Testing with AI: Choose What to Test
You rarely have time to run every test before a release. The real question is which tests matter most this time. In this lesson you will use risk-based regression testing with AI to score risk, choose tests and clearly explain what you are leaving out.
📖 What You’ll Learn
- What regression testing and risk mean
- How to score risk with two simple numbers
- How AI can help map changes to tests
- How to explain what you are skipping
💡 What Is Regression Testing?
Explain Like I’m 5: Regression Testing
Imagine: You fix a wobbly table leg. Then you check that the table still stands and nothing else came loose.
What it really means: Regression testing checks that changes did not break working features.
In testing: After a checkout fix, you also check payments and order emails.
🔍 What Is Risk?
Explain Like I’m 5: Risk
Imagine: Spilling water on the floor is a small problem. Spilling water on a laptop is much bigger.
What it really means: Risk combines how likely a problem is and how much harm it causes.
In testing: A likely bug in payments deserves more testing than a rare logo issue.
Use this simple formula:
Risk score = Likelihood × Impact
Score each from 1 (low) to 3 (high). Your team can adjust the scale.
🌍 Real-Life Example: A Checkout Release
This release changes the discount calculation.
| Area | Likelihood | Impact | Score | Decision |
|---|---|---|---|---|
| Order total and discounts | 3 | 3 | 9 | Test deeply |
| Payment | 2 | 3 | 6 | Test core and negative paths |
| Order confirmation email | 2 | 2 | 4 | Test main path |
| Login | 1 | 3 | 3 | Run smoke test |
| Profile picture | 1 | 1 | 1 | Skip this release |
Likelihood rises when code has changed, is complex or has failed before. Impact rises when a failure affects money, safety, legal duties or many users.
🛠️ How to Do Risk-Based Regression Testing with AI
Explain Like I’m 5: Sorting Your Time
Imagine: You have only ten minutes before bedtime, so you put away the sharp toys first.
What it really means: Limited time should go to the most important risks.
In testing: Run the highest-risk tests first.
AI can help you to:
- Connect a change list to features that may be affected
- Suggest regression areas that you might forget
- Draft a first risk table from your facts
- Summarise your decision for stakeholders
AI does not know your real code dependencies unless you supply them. It also does not know which customers matter most. Ask developers what changed and what else uses that code.
Use real evidence
Base scores on change history, defect history, usage and developer input. An AI score with no evidence is only an opinion.
📌 Say What You Are Not Testing
Explain Like I’m 5: Being Honest
Imagine: You tell your parent, “I tidied my room, but I did not clean under the bed.” Now nobody is surprised.
What it really means: Share what you left out and what risk that creates.
In testing: Stakeholders can accept the risk or ask for more testing.
A clear statement could be:
“We did not retest profile pictures in this release because the code did not change and past defects are low. The remaining risk is low.”
🔑 Automated Regression
Run your stable automated suite on every build when you can. Risk-based choices then focus mostly on manual time and slower tests. Unstable tests weaken confidence, so see Retries and Fixing Flaky Tests.
🧪 Try It Yourself
- Imagine a change to the room search on the Dummy Booking Website.
- List five areas, and score them yourself.
- Run the prompt below with the same facts.
- Compare every score that differs by 2 or more.
- Decide which score is right, and write why.
📋 Ready-to-Copy Prompt
You are a senior QA engineer planning regression testing for a release.
What changed: [change list]
Known dependencies from developers: [dependencies]
Past defects: [defect history]
Important user journeys: [journeys]
Testing time available: [time]
Create a risk table with: Area, Likelihood (1-3), Impact (1-3), Score,
Evidence, Suggested Testing and Reason.
Then list what could be skipped and the risk of skipping it.
Rules:
- Calculate Score as Likelihood multiplied by Impact.
- Use only the information above as evidence.
- Write "[UNKNOWN]" where evidence is missing.
- Mark this as a draft for human review.⚠️ Common Mistakes
- Giving every area a “High” rating
- Accepting an AI risk score that has no evidence
- Ignoring features that share changed code
- Skipping tests without telling anyone
- Using the same regression pack for every release
🎯 Key Takeaways
- Regression testing checks that changes did not break existing features.
- Risk combines likelihood and impact.
- Use real evidence from changes, defects and usage.
- Always make skipped areas and remaining risk visible.
🎤 Interview Questions
1. What is regression testing?
Model answer: Regression testing confirms that recent changes have not broken existing behaviour. It can be a full suite or a selected set, depending on the change and the time available.
2. How do you prioritise regression tests with limited time?
Model answer: I score areas by likelihood and impact, using change details, defect history, usage and developer input. I test the highest risks first and clearly report what was not tested.
3. What is risk-based testing?
Model answer: It is an approach where testing effort follows the level of product risk. Critical, likely problems receive deeper coverage, while low-risk areas may receive lighter checks or none.
4. How can AI help with regression planning?
Model answer: It can map a change list to possible affected areas and draft a risk table. I verify dependencies with developers and base the scores on real data. The final decision remains with the team.
5. What is the difference between smoke testing and regression testing?
Model answer: A smoke test is a quick check that a build’s critical functions work well enough for further testing. Regression testing is broader and checks whether changes have broken existing behaviour.
📝 Assignment
Create a risk table for a made-up release with at least six areas. Write a two-sentence statement for each skipped area. Ask a friend to challenge one score, and record whether your evidence changes your view.
❓ FAQ
Should I always use a 1 to 3 scale?
No. Use the scale your team understands. A simple scale is often enough to support a good discussion.
Can AI select tests automatically?
Some tools use code changes and past results to select tests. They still need trusted data, and teams should check that important tests are not being missed.
🚀 Next Steps
Well done on finishing this lesson. Complete the assignment, then continue with Test Summary Report with AI: Write Results Stakeholders Understand.