BLOG

The first five tests to write when you have none

A practical starting order for a team with zero coverage: the money path, the form, the edge, the regression, and the build itself.

14 November 2026 2 min read #qa-testing#playwright

Zero to test suite is the hardest jump. Teams stall because “testing everything” is a project with no end, and projects with no end never start. So don’t test everything. Test these five, in this order:

1. The money path, end to end

Whatever flow converts a visitor into revenue — signup, checkout, the contact form that generates leads — walk it in a real browser. Click what a user clicks, enter what a user enters, assert the result. One test. If it passes, you can deploy; if it fails, you just saved yourself a very bad afternoon.

If you’re using Playwright, this is a single file: navigate, fill, click, expect. Twenty lines.

2. The form validation

Forms are where users enter the real world into your system — and where most silent breakage hides. Test that valid input succeeds and that invalid input fails with an error message, not with a crash. Include the awkward cases: empty fields, an email with a plus sign, a message ten characters over the limit.

3. The one calculation your business depends on

Every product has one: a price total, a shipping cutoff, a rate conversion, a discount rule. Whatever yours is — it’s the thing a bug in would cost money and trust. Write unit tests for the known-good answers, including the edge cases: zero, negative, the boundary values.

4. The last production bug

Something broke last month. Everyone remembers. Write the test that reproduces it, watch it fail on the pre-fix code, then pass on the fix. This does two things: it proves the bug is dead, and it teaches the team that bugs are input for the suite, not just scars.

5. The build itself

A test that builds the project and deploys to a staging URL. It sounds trivial; it is not. Most catastrophic releases are not logic failures — they’re a build that succeeded locally and failed in the pipeline with a missing file, a bad environment variable, a broken asset path. A build test catches the class of failure that takes the whole site down.

After the five

Notice what you now have: the revenue path guarded, the user input guarded, the critical math guarded, history guarded, and the pipeline guarded. That is a suite — small, high-value, and real. Everything beyond it is compounding interest: every new test covers one more promise, every bug becomes one more tripwire.

This order is how we start every testing engagement. If you want it started for you, that’s literally the first week of the QA service — and if you want to do it yourself, the worked example in our testing article shows the shape we aim for.

Want this handled for you?

Start a project