Test automation that survives the next release

Key points

• Automate the tests that protect the most important journeys first.
• Stable test data matters as much as the test scripts.
• Treat test code with the same care as product code.

Choosing what to automate

Start with the journeys that would hurt most if they broke, and with checks that run often. Leave rare, exploratory checks to people.

Keeping tests useful

Review failing tests quickly, remove tests that no longer add value, and keep test data under control so results can be trusted.

Talk to our quality engineering team