Test Cases & Steps

A test case is the building block of your coverage. You define the steps to take, the assertions to check, and the result you expect, then run that case on its own to confirm a feature behaves correctly. No code required to get started.

Who it’s for#

Business analysts and QA engineers who want to write precise, repeatable tests without scripting.

What it does#

• Steps and assertions — build each case from ordered steps with assertions and expected results.
• Standalone execution — run any test case on its own to check a single feature.
• Bulk import — bring in test cases from Excel so existing work moves over quickly.
• Capability links — connect each case to the features and capabilities it covers for traceability.
• No-code authoring — analysts can write tests directly, without engineering help.

How it works#

You describe the expected behavior as steps and assertions, then link the case to the business feature or capability it verifies. When the case runs, each step is checked against its expected result so you see exactly where behavior diverges.

Why it matters#

Clear, traceable test cases give you confidence at the smallest unit of testing. When a case links to a capability, you always know which part of the business it protects and why it exists.