# Write a test without writing code: steps, checks and values

> A plain-language test is only as good as its checks. How to write steps a tester can follow and checks it can judge, with examples that pass review first time.

By Jason Nguyen, Founder, Testsy. Published 2026-11-21. https://testsy.dev/blog/write-a-test-without-writing-code/

## A test is a brief, not a wish

"Check the app works" cannot fail, so it cannot pass in any useful sense. The difference between a test that catches bugs and one that does not is almost always the checks: whether each one names something on the screen that proves it.

Testsy turns your description into a plan of **steps** (what the tester does) and **checks** (what must be true), and you review the plan before it runs. These are the rules from [the docs](https://testsy.dev/docs/steps-checks-values/), with examples.

![The plan the assistant drafts from your words: numbered steps, the checks, and the options.](https://testsy.dev/docs/img/plan-light.webp)

## Steps: one action each

Steps are what a person would do, in order: open a page, search, click, fill in a form, upload a file, sign in. Keep each to one action. A plan holds up to 30.

Name things the way the screen does. "Click Create workspace" beats "click the button to make a new one", because the tester looks for those words.

## Checks: name the value

Each check is judged on what is visible on the screen, and the result keeps the value it was decided on and where it was read. So a good check says what will be visible when it passes:

| Instead of | Write |
| --- | --- |
| Saving works | After reload, the task still reads "Release smoke sample" |
| Publishing works correctly | The published page shows the heading "Launch notes" |
| Sign-up works as expected | After following the confirmation email, the app shows the new account's workspace |
| The cart is right | The cart total reads "$36.00" for two mugs |

The plan flags a check under four words, or one with "works", "correctly" or "as expected" and no quote or number, before anything runs.

## Values: things to read, not judge

Sometimes you want a number reported without a pass or fail riding on it: an order id, a published address, how many rows a report had. Ask for it as a value to record ("record the order number"). Values appear under **Values seen** with the step they were read at.

![Each passed check with the value it was decided on, the screenshot it was read from, and the step.](https://testsy.dev/docs/img/run-checks-light.webp)

## Assumptions and questions

The plan lists what it takes for granted ("the pricing page is public"). Remove an assumption that is wrong. When only you can answer something, such as which account to sign in with, the plan asks, and a test with an open question waits for your answer.

## A before and after

Before:

```text
Test the booking form.
```

After:

```text
Open https://studio.example.com/book.
Choose the "Deep tissue, 60 min" treatment and the first free time
next Tuesday.
Fill in the name "QA Test", this run's email address and the phone
0400 000 000, and send the booking.
Check the page says "Booking request received" and shows the
treatment and the time chosen.
Wait for the confirmation email and check it names the same
treatment and time.
```

The second one can fail in five specific ways, and each one tells you what broke.

## Or skip the assistant

If you prefer, [write the test yourself](https://testsy.dev/docs/write-it-yourself/) as plain text and let the tester plan at run time. The same rules about checks apply.

This post is part of [Testing an app you built with AI](https://testsy.dev/blog/test-an-app-you-built-with-ai/).
