Add a severity filter to the awesome report (fixes #921) - #920
Open
d-braun wants to merge 5 commits into
Open
Conversation
Adds a severity dropdown next to the existing quick filters, so test
results can be narrowed down to one or more severity levels. Test
results without a `severity` label are selectable as their own option
("no severity"), backed by the `none` sentinel value written to the
tree leaves.
The filter is always visible and its state is kept in the `severity`
url param, in line with the transition filter.
The transition filter rebuilt from the url put `logicalOperator` inside the field instead of on the field filter itself, so `buildFieldFilters` fell back to "AND" and chained the selected transitions with it. Since a test result has exactly one transition, selecting more than one transition matched nothing at all.
d-braun
force-pushed
the
feat/awesome-severity-filter
branch
from
September 2, 2026 14:32
02b35ec to
0f976f2
Compare
d-braun
changed the title
…-filter # Conflicts: # packages/web-awesome/types.d.ts
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
Fixes #921
The awesome report could be narrowed down by transition, tags and categories, but not by severity — even though the severity label is already shown on every test result. This adds a severity dropdown next to the existing quick filters.
severitylabel can be filtered for explicitly.OR, and the selection is kept in theseverityurl param, in line with the transition filter.severitylabel to each tree leaf, falling back to the newnoSeverityValue("none") sentinel fromcore-apiwhen the label is absent.filters.severityand theseverity.*level names, so only the newseverity.noneentry had to be translated.While covering the new filter, the same code path turned out to be broken for transitions: the transition filter rebuilt from the url put
logicalOperatorinside the field instead of on the field filter itself, sobuildFieldFiltersfell back toANDand chained the selected transitions with it. Since a test result has exactly one transition, selecting more than one transition matched nothing at all. That is fixed in a separate commit, with a regression test.Checklist