action #65205
closed
coordination #154768: [saga][epic][ux] State-of-art user experience for openQA
coordination #157345: [epic] Improved test reviewer user experience
[ux][ui][easy][beginner] Result filter on "All tests" page affects running and scheduled job tables size:S
Added by mkittler over 4 years ago.
Updated about 1 month ago.
Category:
Feature requests
Description
Observation¶
The result filter on "All tests" page affects running and scheduled job tables. This is notable when reloading the page after selecting a filter (or adding the URL query parameter manually).
For example https://openqa.opensuse.org/tests?resultfilter=Failed will result in empty tables for scheduled jobs
Problem¶
This is weird considering the filter is within the "Last XXX finished jobs" section and running/scheduled jobs don't have a result anyways. It is also not what I had in mind when adding the filter.
Acceptance criteria¶
- AC1: The result filter does not affect scheduled and running jobs on the "All tests" page - also when present as query parameter when loading the page initially.
Suggestion¶
The tables for running/scheduled jobs should be unaffected by query parameters.
Further details¶
entrance level issue
- Category changed from Regressions/Crashes to Feature requests
- Priority changed from Normal to Low
While I see the problem as you mentioned I see it neither as a regression nor impacting important use cases. Selecting filters is always an explicit choice and I guess users that are able to use the filter learn quickly about this limitation.
- Tags set to ux, ui, easy, beginner, entrance level
- Subject changed from Result filter on "All tests" page affects running and scheduled job tables to [ux][ui][easy][beginner] Result filter on "All tests" page affects running and scheduled job tables
- Description updated (diff)
- Target version changed from future to Ready
- Status changed from Workable to New
Not workable, needs estimation
- Parent task set to #157345
- Subject changed from [ux][ui][easy][beginner] Result filter on "All tests" page affects running and scheduled job tables to [ux][ui][easy][beginner] Result filter on "All tests" page affects running and scheduled job tables size:S
- Description updated (diff)
- Status changed from New to Workable
- Assignee set to robert.richardson
- Status changed from Workable to In Progress
- Status changed from In Progress to Resolved
robert.richardson wrote in #note-10:
That url is not working for me. Please upload screenshots to the ticket instead.
We have this failing test in master now:
https://app.circleci.com/pipelines/github/os-autoinst/openQA/15201/workflows/bf17d820-6fd7-4600-aa79-9b9cb56691d8/jobs/145422
[12:48:23] t/ui/10-tests_overview.t ................... 25/?
# Failed test 'Scheduled jobs are displayed'
# at t/ui/10-tests_overview.t line 633.
# got: '6'
# expected: '4'
# Looks like you failed 1 test of 3.
# Failed test 'result filter does not affect scheduled and running jobs'
# at t/ui/10-tests_overview.t line 637.
[12:48:23] t/ui/10-tests_overview.t ................... 27/? # Looks like you failed 1 test of 27.
[12:48:23] t/ui/10-tests_overview.t ................... Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/27 subtests
Since it's the test you added I'll reopen the ticket, although I don't know why it only started to fail today.
Since it started to fail after merging https://github.com/os-autoinst/openQA/pull/5971 I'll also comment in #166559
- Status changed from Resolved to Workable
- Status changed from Workable to Resolved
Also available in: Atom
PDF