QAM Hub QAM Hub
Home / Glossary / Test step

Test step

Last reviewed

One action within a test case, paired with the result expected after it. Steps make a case executable by someone who did not write it, and they make a failure precise: the run records which step failed, not just that the case did. Cases with a single vague step are the usual reason failures need re-investigation.

Also called: step, test action

How big is one step

A step is one thing a tester does that the product can respond to: click, submit, upload, wait for a job to finish. "Open the cart, apply code SAVE10 and pay" is three steps written as one, and when it fails nobody can say which part broke without running it again. The opposite mistake is splitting every keystroke into its own line. If two actions always happen together and cannot fail separately, they belong in one step.

Step versus test case

A test case checks one behaviour and passes or fails as a whole. Its steps are the route to that behaviour. Steps are not reusable on their own in most teams, and trying to make them reusable by building a library of shared steps tends to produce cases nobody can read without opening five other pages. Reuse belongs at the case or template level.

Every step needs something to check

A step without an expected outcome is an instruction, not a check. "Click Save" tells the tester what to do; "Click Save. The confirmation banner shows the order number" tells them how to judge it. Numbering expectations to match steps (expectation 3 is what step 3 should produce) keeps long cases readable and makes a failed result point at the exact line.

Data belongs in the step

"Log in as a test user" fails the day that user is deleted. Name the account, the product, the coupon, the card, or point to where the data lives. Credentials are the exception: reference the vault entry, do not paste the password.

In QAM Hub

Each test case has a Steps block and an Expected Result block, each with its own attachments, and Run mode shows them one case at a time while testers record results. The writing side is covered in working with steps and expected results and how to write test cases.

Back to the test management glossary