Test explorer
Every test with its runs, failed and flaky share and time lost - sorted worst first, filtered by source, branch, browser and period.
The Test explorer lists every test with a counted run in the period - CI and local runs by default. What each number means is on How Squally measures tests.
Filters
Section titled “Filters”The filters read as a sentence under the title, for example “Showing CI and local runs on all branches from the last 30 days”. Each choice opens a menu:
- Source - “CI and local runs” by default, “CI runs” or “local runs”. Local runs count together with CI runs until you pick one of them - see Overview for why, and pick “CI runs” to read your CI on its own.
- Branch - “all branches” by default, or one branch.
- Browser - “all browsers” or one browser. Shown only when the tests ran in more than one browser in the period.
- Period - the last 7, 14, 30 or 90 days; 30 by default.
The search at the end of the line finds tests by name or file.
The ⓘ after the sentence says what was counted, for example “38 completed CI runs from the last 30 days on all branches, all shards of a run as one, without local runs or runs where most of the suite failed at once.” Under local runs it counts local runs instead, under CI and local runs both. Runs that have not finished yet are not counted; the note says how many there are.
Under the title, one sentence sums up the list, for example “70 tests across 65 CI runs. 3 failed in more than half of their runs, 12 were flaky at least once.” With a search or a browser filter, only the first part is shown.
Columns
Section titled “Columns”| Column | Shows |
|---|---|
| Test | the test’s name; under it its file, the browser it ran in and ⌀ its average duration |
| Runs | how many runs counted |
| Failed % | the share of its runs that failed |
| Flaky % | the share that passed only after a retry |
| Time lost | what its retries and failures cost |
| Last 10 runs | one mark per run, oldest to newest (on wide screens) |
The average duration is the final attempt’s, over the period’s runs. Hover a share for the count behind it, for example “3/20 runs failed”. A share of 0.0% is drawn faint, so the rows that need a look stand out.
On a phone each test is a card: its name and second line, then “15.0% failed · 5.0% flaky · 20 runs” with its last runs beside them.
Worst first: by failed % + flaky %, highest first, by default - the Failed % header shows it. Click a column header to sort by it, highest first; click it again to turn the order around. Ties go to the test with more runs, then by name. A test opens with the list’s order, and Test explorer on its page brings you back to the list as you left it.
Show more
Section titled “Show more”The list shows 20 tests. Under it, “20 of 70” and a Show 20 more button add the next 20; the last step says what is left, for example “Show 6 more”. Changing a filter starts again at 20.
An empty list
Section titled “An empty list”- A search or filter that matches nothing says so, for example “No tests match these filters”, with Clear filters.
- A project with runs, but none from the chosen source in the period, says “No CI runs in this period”.
- A project that has never reported a run says “No test cases found”, with Go to Overview - the setup steps are on the Overview.
A test opens its own page, with the list’s period, branch and source: Test detail. The old flaky list now leads here.