Write a test case
Define a scenario with clear actions and expected results.
Keep each test focused on one outcome, such as signing in or updating a profile. Use Action steps to interact with the app and Verify steps to check the result.
Create and publish
- Open Tests → New test → Structured steps.
- Enter a name, optional description, and severity:
critical,high,medium, orlow. - Add at least one step. Use + to add steps and drag to reorder them.
- Optionally assign suites and tags, then Save as draft or Publish.
Publish the case before running it or adding it to a scheduled suite.
Step types
| Type | Use it for |
|---|---|
| Action | Navigate, click, type, or upload a file. |
| Verify | Check a specific expected outcome. |
| Login | Sign in with a selected project test account. |
| Screenshot | Capture a labeled checkpoint for review in Activity. |
| Wait | Pause for 1–180 seconds; the default is 5. |
Example: update a profile
| Type | Step |
|---|---|
| Login | Select the QA user test account. |
| Action | Open Profile settings and change the display name to “QA Reviewer”. |
| Action | Click Save. |
| Verify | The profile shows “QA Reviewer” as the display name. |
Name the control or data that matters. A check such as “The profile shows QA Reviewer” gives you a clearer pass condition than “Check that saving worked.” Use a test account with the permissions and starting data the flow needs.
Test accounts and files
Add a Login step and select a saved test account. You can also type @ in Action or Verify text to select a test account or project asset by label.
For upload flows, attach an asset to the step or select it with @. Test accounts and assets are shared across the project's run targets, so check that the selected account works on the target environment.
Next, run the test or add it to a suite.