Test cases define how to verify that a feature or fix works correctly. Each test case describes the steps to follow and the expected outcome. You can link test cases to user stories for full traceability from requirement to verified delivery.
Silverile also integrates with the VS Code extension to generate test scripts automatically from acceptance criteria — see the VS Code Extension guide for details.
| Field | Required | Notes |
|---|---|---|
| Title | Yes | Short description of what is being tested. |
| Description | No | Context and background for the test. What system state is assumed. |
| Preconditions | No | Setup steps required before the test can be executed — e.g. "User must be logged in as Admin". |
| Test Steps | Yes | Numbered steps to perform the test. Each step should be a single, specific action. |
| Expected Result | Yes | What should happen if the system behaves correctly after all steps are completed. |
| Linked Story | No | The user story or acceptance criterion this test case validates. |
| Priority | No | How critical this test is — High, Medium, or Low. |
Linking a test case to a user story gives you full traceability — you can see which acceptance criteria are covered and which stories have no test coverage yet.
Open a story's detail view and go to the Test Cases tab to see all test cases linked to that story, and to add new ones directly from there.
Test cases are executed within a test run — a snapshot of selected test cases at a point in time (e.g. for a sprint or release).
For each test case in a run, record one of the following outcomes:
| Result | When to use it |
|---|---|
| Pass | The system behaved exactly as described in the Expected Result. |
| Fail | The system did not match the expected result. A defect should be filed. |
| Blocked | The test could not be executed due to an environment issue or a dependency. |
| Skipped | The test was intentionally not run in this cycle. |
When a test fails, you can create a defect directly from the test result — click File Defect and the defect form pre-fills with the test case title and steps.
I don't see a Test Cases section in the sidebar
Test case management may need to be enabled for your project under Project Settings. Ask your project manager to enable it if it's not visible.
I can't link a test case to a story
Test cases can be linked to stories within the same project. Search for the story by ID or title in the Linked Story field. If the story is in a different project, you can reference it by ID in the description.
Test results aren't being saved
Results are saved per execution run. Make sure you've started a test run before recording results — you can't record a pass/fail directly on a test case without an active run.
A team member can't see the test cases I created
Test cases follow project access controls. Confirm the team member has at least read access to the project. Read-only members can view test cases but cannot create or execute them.
I want to generate test cases from a story automatically
The Silverile VS Code extension can generate test scripts from acceptance criteria. Open VS Code, right-click in a code file, and choose Silverile → Generate Test Scripts from Story, then enter the story ID.