Automated testing for business applications: where to start

Automated tests let a team change software confidently. The question is where to start when time is limited.

Test the business rules

Calculations, approvals, limits and status changes are where errors are most expensive. Unit tests for these rules are fast and valuable.

Cover critical journeys end to end

A handful of end-to-end tests for the most important user journeys — placing an order, registering a patient, closing a month — catch integration problems.

Run tests on every change

Use continuous integration to run tests automatically before changes are merged and deployed.

Add a test for every bug

When a bug is fixed, add a test that would have caught it. Coverage grows where it matters.

Keep tests reliable

Flaky tests are ignored. Use stable test data and avoid dependence on timing or external services.

See how we build reliable business software.