Add test configuration templates for charmcraft
Metadata
Current evaluation
Test init profiles delivered by merged PR #2401 (commit a7334d49), adding test-machine and test-kubernetes templates for `charmcraft init`; shipped in Charmcraft 4.0.
Resolution: closed resolved
Reason: PR #2401 'feat(test): add testing profiles for init command' was merged as commit a7334d49, adding the test-machine and test-kubernetes init profiles requested here. The Charmcraft 4.0 release notes confirm the two profiles shipped, with later refinements in #2312, #2430 and #2873.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### What needs to get done
Write the template files for the craft-application testing infrastructure files. The files are added to a project using `charmcraft --init --profile=test`.
### Why it needs to get done
To give new users a simple working set of test configuration files to build upon.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Test init profiles delivered by merged PR #2401 (commit a7334d49), adding test-machine and test-kubernetes templates for `charmcraft init`; shipped in Charmcraft 4.0. | |
| stealth/space-bunny-alpha | — | closed resolved | Testing templates shipped in merged PR #2401 (commit a7334d49), adding test-machine and test-kubernetes profiles for charmcraft --init in Charmcraft 4.0. | |
| stealth/space-bunny-alpha | — | closed resolved | Testing configuration support was delivered by merged PR #2401 (commit a7334d49), adding test-machine and test-kubernetes profiles for charmcraft --init. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. The request to add test configuration templates for charmcraft via charmcraft --init --profile=test was abandoned, with only an automated Jira sync comment recorded. | |
| qwen/qwen3.6-35b-a3b | — | — | Request for charmcraft test configuration templates was closed without implementation. An automated sync created internal Jira ticket CHARMCRAFT-632. No pull request or code changes were merged, indicating the task was superseded by the internal ticket. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The request was synced to an internal Jira ticket but no pull request was opened or merged. The feature remains abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The request to add test configuration templates via charmcraft --init --profile=test was deferred, with tracking moved to internal Jira ticket CHARMCRAFT-632. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. Only an internal Jira ticket was created, with no code changes or merge recorded. The request appears abandoned. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/charmcraft#2401
(confidence 97%)
Merged PR adding test-machine/test-kubernetes init profiles, the concrete resolution of the template request
-
Related To:
canonical/charmcraft#2312
(confidence 60%)
Follow-up switching the kubernetes/machine profile templates to uv for testing and packing
-
Related To:
canonical/charmcraft#2430
(confidence 55%)
Follow-up migrating the profile templates' integration tests to Jubilant
-
Related To:
canonical/charmcraft#2873
(confidence 40%)
Later enhancement of init profile support (base-specific profiles)
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2401 feat(test): add testing profiles for init command | charmcraft | merged | Merged PR #2401 as commit a7334d49, adding test-machine and test-kubernetes init profiles for charmcraft test; the feature shipped in Charmcraft 4.0. | |
| #1384 Add `config` example to templates | charmcraft | closed | Added commented sample config sections to all Charmcraft init templates, fixing the Kubernetes and machine profile inconsistency. Merged in PR #1476 as commit 67f314a1. | |
| #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. | |
| #1113 Clean up test template, make test code self-explanatory | charmcraft | closed | Charmcraft 4.0 template updates resolved the request: PR #1551 (commit daf5a5b9) migrated generated unit tests from unittest to pytest functions/fixtures and plain assertions. | |
| #1660 feat: add test command and templates | charmcraft | merged | Merged as commit 097a4e9a, adding `charmcraft test` with templates for local or remote Spread suites using a Multipass backend. | |
| #328 charmcraft init produces error charm for machine charms | charmcraft | closed | Machine charms gained a dedicated charmcraft init profile, resolving Kubernetes-only initialization; the change was merged in PR #868 (commit 2ed9033c). | |
| #859 Added a kubernetes profile to init command (CRAFT-1318). | charmcraft | merged | Merged in canonical/charmcraft#859 (451c399a), adding the Kubernetes init profile and fixing the simple template for CRAFT-1318. | |
| #762 Dynamically import charmcraft init template | charmcraft | closed | Closed in favor of broader charmcraft init profile work, notably #568; live template-repository fetching was left for future discussion. Profile support later landed through PRs #854, #859 and #868. | |
| #2312 feat(templates): use uv for testing and packing kubernetes and machine charms | charmcraft | merged | PR merged as commit e451f70f: charmcraft init kubernetes/machine profiles now use pyproject.toml deps, tox-uv, the uv plugin for packing, and a uv.lock template; docs updated, requirements-dev.txt page removed. | |
| #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. |