test: update charm integration test
Metadata
Current evaluation
Merged in canonical/craft-actions#132 (54f7849), updating the charm pack integration test to use another simple charm after the previous Juju fixture was removed.
Resolution: closed resolved
Reason: PR #132 was merged as commit 54f7849. It replaced the removed charm fixture with testcharms/charms/dummy-source, and the reported CI checks passed.
Evaluated by: mr-cal-bot
No scores available.
Issue body
The previous charm input was removed from the juju repository, so this picks out a different and similarly simple charm for pack testing.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| minimax/minimax-m3.1-flash:free | — | closed resolved | Merged in canonical/craft-actions#132 (54f7849), updating the charm pack integration test to use another simple charm after the previous Juju fixture was removed. |
Update history
| Date | Change |
|---|---|
| merged | |
| updated | |
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1198 tests: add charm library multiple versions update test | charmcraft | merged | Merged PR #1198 (commit 154bf5d6) added a 120-line regression test covering updates across multiple charm-library versions, linked to #1020/CRAFT-1916. | |
| #1235 tests: re-enable reactive charms test | charmcraft | merged | Merged PR canonical/charmcraft#1235 as commit bff2a6a3, re-enabling the reactive charms test with a one-line change after two approvals. | |
| #2364 Update charmcraft test to use the new testing infrastructure | charmcraft | closed | Fixed by merged PR charmcraft#2385 (commit b7730efc), replacing Charmcraft’s custom test command with craft-application’s upstream test infrastructure. | |
| #2695 feat(templates): add juju_setup to integration tests, improve comments, fix resolve() | charmcraft | merged | Merged in charmcraft PR #2695 (commit 74d12bce), adding juju_setup to generated integration tests, clarifying comments, and removing redundant resolve(). | |
| #2426 fix(test): fix the reactive charm spread test | charmcraft | merged | Merged in canonical/charmcraft#2426 via commit 7c33dd1b, applying a one-line fix to the reactive-charm spread test for CHARMCRAFT-641. | |
| #49 ci: test the charmcraft actions in more places | craft-actions | merged | Merged PR #49 in commit a8e5310, expanding Charmcraft action CI coverage across more Ubuntu architectures, channels, and pinned-revision runs. | |
| #743 Check the resulting packed charm to ensure Juju will be able to use it | charmcraft | closed | Juju-based verification was obviated by charmcraft test, added in merged PR #1660 (commit 097a4e9a) and released in Charmcraft 3.1. | |
| #1540 fix: template integration tests | charmcraft | merged | Merged PR #1540 as commit f3f82031, updating integration-test templates to use charmcraft.yaml instead of metadata.yaml and completing the stalled change from #1468. | |
| #439 [docs] how to run charmcraft as part of a CI? | charmcraft | closed | Closed as addressed: canonical/craft-actions#31 (commit 91513c1) added Charmcraft setup and pack actions, and a maintainer confirmed CI packing and publishing were now supported. | |
| #2385 feat!(test): switch from the custom test command to upstream | charmcraft | merged | Merged PR charmcraft#2385 (commit b7730efc) for CHARMCRAFT-631, replacing charmcraft's custom 'test' command with craft-application's upstream test infrastructure; it fixes and closes issue #2364. Some spread tests on 20.04/22.04 still fail. |