ci: Execute rest_api_test tests in codeconv

[sergio-costas]

The tests in the rest_api_test.go file require dbus-launch, available in dbus-x11. If that binary isn't available, the tests are skipped.

A clear proof of this are the Codecov checks, which show that the code in rest_api.go isn't being checked, even when there are tests that cover it.

This patch fixes this.

Thanks for helping us make a better snapd!
Have you signed the license agreement and read the contribution guide?

[github-actions]

Fri Feb 27 12:15:21 UTC 2026
The following results are from: https://github.com/canonical/snapd/actions/runs/22479051640

Failures:

Preparing:

• openstack:ubuntu-core-24-64:tests/main/apparmor-prompting-support
• openstack:ubuntu-20.04-64:tests/main/nss-modules:winbind
• openstack:ubuntu-25.10-64:tests/main/apparmor-prompting-integration-tests:create_multiple_deny

Executing:

• openstack:ubuntu-core-20-64:tests/core/snapd-maintenance-msg
• openstack:ubuntu-core-20-64:tests/core/services
• openstack:ubuntu-core-24-64:tests/core/kernel-base-gadget-pair-single-reboot-failover:gadget_base
• openstack:ubuntu-core-24-64:tests/core/kernel-base-gadget-single-reboot-failover
• openstack:ubuntu-core-24-64:tests/main/dbus-activation-session
• openstack:ubuntu-core-24-64:tests/main/snap-user-service-upgrade-failure
• openstack:ubuntu-25.10-64:tests/unit/go:clang
• openstack:ubuntu-25.10-64:tests/main/auto-refresh-gating
• openstack:ubuntu-25.10-64:tests/main/apparmor-prompting-snapd-startup
• openstack:ubuntu-25.10-64:tests/main/appstream-id

Restoring:

• openstack:ubuntu-core-20-64:tests/core/snapd-maintenance-msg
• openstack:ubuntu-core-20-64:tests/core/
• openstack:ubuntu-core-20-64:
• openstack:ubuntu-core-24-64:tests/core/kernel-base-gadget-pair-single-reboot-failover:gadget_base
• openstack:ubuntu-core-24-64:tests/core/
• openstack:ubuntu-core-24-64:
• openstack:ubuntu-core-24-64:tests/core/kernel-base-gadget-single-reboot-failover
• openstack:ubuntu-core-24-64:tests/core/
• openstack:ubuntu-core-24-64:
• openstack:ubuntu-25.10-64:tests/main/apparmor-prompting-snapd-startup
• openstack:ubuntu-25.10-64:tests/main/
• openstack:ubuntu-25.10-64:

Skipped tests from snapd-testing-skip

• openstack:ubuntu-24.04-64:tests/main/i18n

[sergio-costas]

Or maybe... should we install the package in the tests themselves...?

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.88%. Comparing base (8d929ea) to head (e83eef8).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #16653      +/-   ##
==========================================
+ Coverage   77.52%   78.88%   +1.35%     
==========================================
  Files        1359     1358       -1     
  Lines      187225   187223       -2     
  Branches     2446     2446              
==========================================
+ Hits       145152   147695    +2543     
+ Misses      33298    30534    -2764     
- Partials     8775     8994     +219     

Flag	Coverage Δ
unittests	78.88% <ø> (+1.35%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[sergio-costas]

Codecov changes:

[sergio-costas]

@olivercalder What do you think? Should I add dbus-x11 in each test, or keep it in the control file?

[sergio-costas]

I moved it to the tests only.

[olivercalder]

I think we need a solution which works when running unit tests locally via ./run-checks as well as in spread and in GitHub CI. The current approach only works in GitHub CI it seems.

I think this should either be packaging as a dependency of snapd, or at least a build-dep. Or it's something we'll want to demand when running ./run-checks, similar to what we do for clang-format.

@bboozzoo will know better than I do, though :)

[sergio-costas]

Then an extra step would be to check in ./run-checks if dbus-launcher is available, and abort if not... What do you think? @bboozzoo ?