Test scenarios, defect triage and regression

Functional and end-to-end testing before UAT, classifying issues correctly, and regression testing.

In this lesson

Writing and running test scenarios
Classifying issues: five kinds
Regression testing

Key points

Scenarios from criteria: preconditions, steps, data, expected results
Test end to end; validate developer work before UAT
Classify: defect, configuration, data, training, change request
Regression pack before every release

Real-world example

During UAT a user reported 'Odoo doesn't calculate VAT'. Classification showed the product had no tax set: a data issue from migration, not a defect. Fixing the import template's tax column for 140 products and re-running the regression pack closed it in a day, with no code change.

Questions and answers

Name the five issue classes.

Defect, configuration issue, data issue, training/user issue, new requirement/change request.

What should happen before UAT?

Internal functional, end-to-end and regression testing, plus validation of developer work.

Read the full lesson, worked example and quiz