Creating and Managing Test Cases
Test cases are structured descriptions of how to verify that a feature or fix works correctly. Varai Sprints's built-in test management lets you create, organize, and track test cases alongside the tasks and issues they validate.
What is a test case?
A test case is a documented scenario that describes:
- What to test (the feature or behavior being verified)
- Preconditions (what needs to be set up before testing)
- Steps (the exact actions to take)
- Expected result (what should happen if everything works correctly)
Good test cases make testing repeatable — anyone on the team can run the same test and get consistent results.
Creating a test case
- In the left sidebar, click Test Cases.
- Click New Test Case.
- Fill in the form:
| Field | Required? | Description |
|---|---|---|
| Title | Yes | A clear label for what is being tested (e.g., "User can reset password via email") |
| Description | No | Overview of what this test covers |
| Preconditions | No | What must be true before running this test |
| Steps | Yes | Numbered steps to execute the test |
| Expected result | Yes | What should happen if the test passes |
| Priority | No | How critical is this test? |
| Status | Auto | Draft, Active, Deprecated |
| Tags | No | Labels for organizing test cases |
| Linked issue | No | Link this test case to the issue it validates |
- Click Create Test Case.
Writing good test steps
Test steps should be specific and unambiguous. Each step should describe one action.
Example test case — Reset password:
Preconditions: User has an account with email
test@example.com. User is not logged in.Steps:
- Go to the sign-in page.
- Click "Forgot password?"
- Enter
test@example.comin the email field.- Click "Send reset link."
- Open the email inbox for
test@example.com.- Click the password reset link in the email.
- Enter a new password that meets requirements.
- Click "Reset password."
Expected result: User is redirected to the sign-in page with a success message: "Your password has been reset."
Test case statuses
| Status | Meaning |
|---|---|
| Draft | Being written, not ready for execution |
| Active | Ready to run |
| Deprecated | No longer relevant (feature changed or removed) |
Running a test case
To record the result of running a test:
- Open the test case.
- Click Run Test.
- Select a result:
- Pass — the test passed as expected
- Fail — the test did not produce the expected result
- Blocked — the test could not be run (e.g., a prerequisite was not ready)
- Skip — test intentionally not run this cycle
- Add a note if needed (e.g., describe what failed).
- Click Save Result.
Each run is recorded in the test case's Run History — you can see who ran it, when, and what the result was.
Organizing test cases
Use Tags to organize test cases into logical groups:
- By feature area:
auth,payments,profile - By test type:
smoke,regression,edge-case - By platform:
mobile,desktop,api
Filter the test case list by tag to quickly find all tests for a specific area.