Have a way for charmcraft to run the tests
Metadata
Current evaluation
Rejected. The maintainer closed the issue, stating a dedicated test command is unnecessary. Users can run tests by configuring override-build in charmcraft.yaml to execute pytest after the build step.
Suggested action: —
No scores available.
Issue body
Charm tests needs to be run by charmcraft. We can add a `test` command, for that.
This is because the charm building can be complex, and will be specified in `charmcraft.yaml`, so no need to duplicate that specification (and the environment building) outside of charmcraft.
A wonderful side benefit of this is that will be trivial to run the tests in all the supported platforms.
That said, we need for `charmcraft test` by default to be super fast (without any noticeable overhead), otherwise developing a charm will be a pain in the neck. We probably should run the tests in only one platform by default (maybe in the newest of the specified ones), but even so...
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 | — | — | Rejected. The maintainer closed the issue, stating a dedicated test command is unnecessary. Users can run tests by configuring override-build in charmcraft.yaml to execute pytest after the build step. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed as unnecessary. The maintainer confirmed that tests can already be executed during the build process using the override-build directive in charmcraft.yaml, making a dedicated test command redundant. | |
| qwen/qwen3.6-35b-a3b | — | — | The proposed test command was rejected. The maintainer closed the issue, noting that tests can already be executed using the existing override-build directive in charmcraft.yaml, rendering additional machinery unnecessary. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Rejected. The proposed test command and pre-pack-hook were deemed unnecessary. Users can already run tests during the build process by appending commands to the override-build directive in charmcraft.yaml, making special machinery redundant. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. Maintainer resolved by noting existing override-build directives in charmcraft.yaml already allow running tests during the build process, eliminating the need for a dedicated test command. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1212 POC charmcraft test command | charmcraft | closed | Closed without implementation. The charmcraft test command prototype and test.yaml structure were abandoned. No comments, development, or resolution occurred. | |
| #2364 Update charmcraft test to use the new testing infrastructure | charmcraft | closed | Updating charmcraft tests to use craft-application's new testing infrastructure was closed without implementation. No pull requests or code changes were submitted, indicating the task was abandoned or deferred. |