Test Steps
Define step-by-step execution procedures for test cases with ordered actions and expected results.
Test Steps
Test steps define the exact procedure a tester follows when executing a test case. Each step has three parts:
- Step — The action the tester should perform (e.g., "Click the Login button").
- Test Data — Optional input data for that step (a URL, a set of credentials, a request payload).
- Expected Result — What should happen after the action is performed (e.g., "User is redirected to the dashboard").
Adding steps
- Open a test case and go to the Test Steps tab.
- Click + Test Step above the step list. A new empty row is appended.
- Fill in Step, optionally Test Data, and Expected Result.
- Repeat for each additional step. Steps are automatically numbered sequentially.
- Click Save to commit your changes. Steps are not saved as you type — the Save button stays enabled until every pending change has been written.
Reordering steps
Use drag-and-drop () to reorder steps. Grab the drag handle on the left side of any step and move it to the desired position. Step numbers update automatically.
Editing and deleting steps
Click on any step field to edit it, then click Save. To delete a step, click the delete icon () on the right side of the step row. The remaining steps are renumbered automatically.
There is no cap on the number of steps you can add by hand. CSV and Excel imports are capped at 50 steps per test case — additional step rows beyond that are dropped for that test case.
Example: Login functionality test case
Below is a sample test case with well-structured steps. Notice how each step contains exactly one action and one expected result.
| # | Step | Test Data | Expected Result |
|---|---|---|---|
| 1 | Open the application URL in the browser | https://app.example.com/login | The login page is displayed with email and password fields |
| 2 | Enter a valid email address in the email field | [email protected] | The email is accepted without validation errors |
| 3 | Enter the correct password in the password field | The password field shows masked characters | |
| 4 | Click the "Sign In" button | A loading indicator appears briefly, then the user is redirected to the dashboard | |
| 5 | Verify the dashboard displays the user's name in the top-right corner | The logged-in user's full name is visible in the header navigation |
Keep steps atomic — each step should describe exactly one action. This makes it easier for testers to identify which specific action caused a failure, and it produces more granular execution reports.
See also
- Test Cases — Overview, creation, detail tabs, and field reference
- Folders & Organization — Organize test cases with folders, search, and filters
- Import & Export — CSV import and export
- Bulk Operations — Clone and bulk update test cases
- History & Attachments — Execution history, change tracking, and file attachments
- Versioning — Automatic version tracking and execution version recording
- Best Practices — Guidelines and FAQ