-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add group filter options for /tests #5401
Conversation
b953c0b
to
66a6b30
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5401 +/- ##
=======================================
Coverage 98.37% 98.37%
=======================================
Files 389 389
Lines 37548 37613 +65
=======================================
+ Hits 36936 37001 +65
Misses 612 612 ☔ View full report in Codecov by Sentry. |
66a6b30
to
b1c6766
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The naming seems... awkward, but it looks pretty good and I honestly don't have a better suggestion so I guess I'm fine with it
Naming is at least consistent with the other PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Care to add some documentation or help text?
Where and in what form? I believe the |
That is correct. How about to mention them all as hover text on the "Search:" label like visible on https://openqa.opensuse.org/tests/ ? |
Sure, but not in this PR. I do not want to touch unrelated features here and create a scope creep situation. |
Based on #5388, and reusing most of the same logic, to bring job group filtering to `/tests` from `/tests/overview`. Similar to the `?match=...` option, this does not have a UI element yet and can only be used by manually entering the query parameter. Since the question of how to extend the filter form with text fields is still open, i consider it out of scope for this PR. Progress: https://progress.opensuse.org/issues/134933
b1c6766
to
69e8e80
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
perfect!
This is a followup for #5388 and #5401. When there were no matches for job group globs, no query condition would be generated previously. Giving the false impression that all job groups were matching. So now we just generate an impossible query that cannot match anything with the group id `0`. Progress: https://progress.opensuse.org/issues/134933
This is a followup for #5388 and #5401. When there were no matches for job group globs, no query condition would be generated previously. Giving the false impression that all job groups were matching. So now we just generate an impossible query that cannot match anything with the group id `0`. Progress: https://progress.opensuse.org/issues/134933
Based on #5388, and reusing most of the same logic, to bring job group filtering to
/tests
from/tests/overview
. Similar to the?match=...
option, this does not have a UI element yet and can only be used by manually entering the query parameter. Since the question of how to extend the filter form with text fields is still open, i consider it out of scope for this PR.Progress: https://progress.opensuse.org/issues/134933