Project

General

Profile

Actions

action #158688

closed

Display only failures in bats-user-local_tap

Added by ph03nix 7 months ago. Updated 7 days ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
2024-04-09
Due date:
% Done:

0%

Estimated time:

Description

When the podman test "bats-user-local_tap" fails, the "Show only failures" function in openQA still displays all subtests. It would be great, if when using "Show only failures" only the failing tests are being displayed, in the same way as for LTP.

Example: The failures in bats-user-local_tap - when setting "Show only failures" I still get the full list of test failures:


Acceptance criteria

  • Ensure the "Show only failures" function of openQA works with the subresults of the "bats-user-local_tap" test

Files


Related issues 1 (1 open0 closed)

Related to Containers and images - action #167353: Re-enable podman integration test runs once they are stableIn Progressrbranco2024-09-25

Actions
Actions #1

Updated by rbranco 6 months ago ยท Edited

Perhaps related:
bats uses the TAP format while img_proof & ltp use IPA. Perhaps a limitation in the parser?

Actions #2

Updated by rbranco 6 months ago

Fwiw, it works on the External tab.

Asked in #eng-testing:
https://suse.slack.com/archives/C02CANHLANP/p1713275967130139

Actions #3

Updated by rbranco 6 months ago

This would need some clever refactoring since we're uploading 4 files instead of just one:

Matthias Griessmeier
yes, because it treats bats-user-local_tap as a single testmodule which as a whole can fail, but not the "external results" inside the test module.
(for that there is the second tab)
I didn't know that feature before, but this is expected behaviour for me

Oliver Kurz
yeah, the checkbox is effectively an "Show only test modules with failures", not "show only failed test steps". The question I have is rather why there are 600+ test steps and if that can be better segmented. I don't know how those tests are structured so I don't have an answer

Actions #4

Updated by ph03nix 6 months ago

@rbranco this is just a nice-to-have. If the required effort exceeds the rather cosmetic advantage, then I think we should not bother too much.
However I want to leave the decision on where to draw the line between worthwhile and too much effort to you.

Actions #5

Updated by rbranco 6 months ago

  • Status changed from Workable to Rejected

After some evaluation, the refactoring needed for this far outweighs the benefits when we already have this functionality in another tab.

Actions #6

Updated by ph03nix about 1 month ago

  • Tags set to bats
Actions #7

Updated by ph03nix about 1 month ago

  • Related to action #167353: Re-enable podman integration test runs once they are stable added
Actions #8

Updated by ph03nix 7 days ago

  • Tags changed from bats to containers
Actions

Also available in: Atom PDF