Test execution is done through test runs — a named collection of test cases executed at a point in time against a specific build, sprint, or release. A run gives you a snapshot of quality at that moment and produces a pass/fail record that can be referenced later.
When a test case fails during execution, you can file a defect directly from the run with the test context pre-filled — no copy-pasting steps required.
Open the run to see the full list of test cases. Work through them one at a time:
| Result | When to use it |
|---|---|
| Not Started | Test case is in the run but hasn't been executed yet. |
| Pass | Executed and the system behaved as expected. |
| Fail | Executed and the system did not match the expected result. A defect should be filed. |
| Blocked | Could not be executed — environment issue, missing data, or a dependent defect. |
| Skipped | Intentionally not run in this cycle — noted for future runs. |
When a test case fails, file a defect immediately while the failure is fresh. Silverile pre-fills the defect form with the test context so you don't have to re-enter the steps.
| Pre-filled field | What gets populated |
|---|---|
| Title | Pre-filled from the test case title. Edit to be more specific about the failure. |
| Description | Pre-filled with the test steps and the expected vs. actual result. Add observed behaviour and any error messages. |
| Severity | Set manually — choose based on the impact of the failure. |
| Linked Test | Auto-linked to the test case that failed. Preserved for traceability. |
| Attachment | Add a screenshot or screen recording before saving — this saves significant investigation time. |
When all test cases have been executed (or you've decided to stop), mark the run complete:
Completed runs are preserved in the Runs history. The pass rate and any linked defects remain visible for audits and retrospectives.
I can't find the test run I created
Test runs are listed under Test Cases → Runs. Use the status filter to show In Progress or Completed runs. Runs don't appear in the main test case list — look for the Runs tab.
The "File Defect" button isn't available after marking a test as Failed
The File Defect button appears only when a test case is marked as Fail within an active test run. If you recorded a Fail outside of a run, open the run, find the test case, and use the button from there.
The defect I filed from a test run isn't showing in the Defect List
The defect is created in the project's defect tracker immediately. Refresh the Defect List page. If still missing, check that you're viewing the correct project.
I can't edit a test result after saving it
Results within a run can be updated as long as the run is still In Progress. Open the run, find the test case, and click the result to change it. Once a run is marked Complete, results are locked.
A team member can't see the test run
Test runs follow project access. Confirm the team member has project access. Read-only members can view runs but cannot record results.
I want to re-run only the failed tests from a previous run
When creating a new run, choose "Import from previous run" and filter to Failed and Blocked cases only. This creates a focused regression run without re-testing cases that already passed.