feat: add test cases from upstream bluefin issue triage#193
Merged
castrojo merged 1 commit intoJun 19, 2026
Merged
Conversation
Add 4 P1 test cases from upstream ublue-os/bluefin issue triage (projectbluefin#12): 1. bluefin#4471 — gnome-software high CPU after close: opens Bazaar, closes it, waits 30s, asserts CPU usage < 5%. Added to tests/software/features/flatpak.feature with a custom step that parses ps CPU output against a named threshold constant. 2. bluefin#4655 — btrfs compression not enabled on root: new tests/system/features/filesystem.feature checks findmnt mount options for 'compress' when root is btrfs. Skips gracefully on non-btrfs filesystems. 3. bluefin#4209 — ujust devmode prompts when already enabled: new tests/developer/features/devmode.feature runs ujust devmode and asserts the output does not contain re-enable prompts. Falls back to plain 'just' if ujust is not on PATH. 4. bluefin#4403 — flatpak repair after Fedora upgrade: new tests/smoke/features/flatpak_health.feature verifies both 'flatpak repair --user' and '--system' exit cleanly. Ref: projectbluefin#12 Signed-off-by: unknown <unknown@users.noreply.github.com>
hanthor
approved these changes
Jun 6, 2026
hanthor
left a comment
Member
There was a problem hiding this comment.
LGTM — well-structured test/infra addition, clean code.
6 tasks
hanthor
approved these changes
Jun 16, 2026
hanthor
left a comment
Member
There was a problem hiding this comment.
Approved via org-wide review.
hanthor
approved these changes
Jun 16, 2026
hanthor
left a comment
Member
There was a problem hiding this comment.
Approved via org-wide review.
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
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.
Summary
Implements the 4 P1 test cases from upstream ublue-os/bluefin issue triage (#12):
1. gnome-software high CPU after close (bluefin#4471)
File:
tests/software/features/flatpak.featureOpens Bazaar, closes it, waits 30s, then checks
ps -C gnome-software -o %cpu=is below 5%. Uses a named constantGNOME_SOFTWARE_CPU_THRESHOLD_PCTin the step definition.2. btrfs compression not enabled on root (bluefin#4655)
File:
tests/system/features/filesystem.feature(new)Checks
findmnt / -o OPTIONSforcompressmount option when root is btrfs. Gracefully skips on non-btrfs filesystems (e.g. ext4 in CI VMs).3. ujust devmode re-enable prompt (bluefin#4209)
File:
tests/developer/features/devmode.feature(new)Runs
ujust devmode(withjustfallback) and asserts the output does not contain phrases like "would you like to enable" or "enable developer mode" — the bug was that it prompted to enable when already active.4. flatpak repair after Fedora upgrade (bluefin#4403)
File:
tests/smoke/features/flatpak_health.feature(new)Verifies both
flatpak repair --userandflatpak repair --systemexit 0. Uses the existingLast command output stripped containsstep from the smoke suite.Ref: #12
Test plan
python3 -m py_compilepasses on all modified/new step files--dry-run