Add testing framework?
Metadata
Current evaluation
Rockcraft now exposes an upstream-backed rockcraft test command for built-rock testing; commit a6d1b77a added it, and downstream CI supports its implicit pack-and-test flow.
Suggested action: close resolved
Reason: Commit a6d1b77a from PR #869, titled "feat: add 'test' command", registered appcommands.TestCommand, which remains exposed in the current CLI. Merged canonical/craft-actions#40 also added support for rockcraft test and its implicit pack step, confirming delivery of the requested built-rock validation capability.
Evaluated by: mr-cal-bot
Impact:
65
Quick Win:
22
Complexity:
52
Confidence:
97
Actionability:
72
Issue body
It could be handy to have a testing framework in the spirit of [cst](https://github.com/GoogleContainerTools/container-structure-test), that is auto-executed after a `pack` is complete, similar to `health-check` in [multipass blueprints](https://github.com/canonical/multipass-blueprints/blob/6a46d02e2db095c8e738f44c18584b4c96dc2e29/v1/docker.yaml#L146).
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
65
Quick Win:
22
Complexity:
52
Confidence:
97
Actionability:
72
|
close resolved | Rockcraft now exposes an upstream-backed rockcraft test command for built-rock testing; commit a6d1b77a added it, and downstream CI supports its implicit pack-and-test flow. | |
| stealth/space-bunny-alpha |
Impact:
55
Quick Win:
5
Complexity:
78
Confidence:
90
Actionability:
40
|
needs triage | Requested post-pack validation framework for built rocks, inspired by container-structure-test and Multipass health checks; remains open, unlabeled, and without maintainer input or implementation. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
5
Complexity:
60
Confidence:
70
Actionability:
40
|
needs triage | Feature request to add a testing framework for built rocks, similar to container-structure-test, auto-executed after pack completes. No maintainer response in 1327 days. | |
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
12
Staleness:
85
Complexity:
70
Confidence:
70
Support Request:
0
|
needs triage | Feature request to add a testing framework to rockcraft, auto-executed after pack, similar to container-structure-test. No maintainer response or labels; no evidence the feature was implemented. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
65
Confidence:
70
Support Request:
10
|
needs triage | Suggests adding an automated testing framework that runs after pack completion, similar to container-structure-test. Unlabeled, no maintainer response, inactive for over 3 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
50
Confidence:
85
Support Request:
5
|
close stale | Suggests adding an automated post-pack testing framework similar to container-structure-test. Open for over 3 years with no maintainer response, labels, or comments. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
rockcraft#869
(confidence 98%)
Its resolving commit a6d1b77a added the rockcraft test command.
-
Related To:
canonical/craft-actions#40
(confidence 94%)
Merged downstream CI support explicitly covers rockcraft test and its implicit pack step.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #40 feat(rockcraft-pack): support rockcraft test | craft-actions | merged | Merged #40 as commit 05e3417, adding rockcraft test support to rockcraft-pack so test workflows can reuse the action's packed rock. | |
| #98 Use `rockcraft test` to test the rocks | snapcraft-rocks | open | Maintainer-filed task to replace/augment spread tests in spread.yaml and CI workflows with `rockcraft test` so built snapcraft rocks are exercised; untouched for 421 days, no labels or discussion. |