Update charmcraft test to use the new testing infrastructure
Metadata
Current evaluation
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.
Suggested action: —
No scores available.
Issue body
### What needs to get done
Charmcraft must be updated to use the new testing infrastructure provided by craft-application.
### Why it needs to get done
The new testing infrastructure will be used in an uniform way across all craft applications.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 | — | — | 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. | |
| qwen/qwen3.6-35b-a3b | — | — | The request to update charmcraft tests for the new infrastructure was closed after 357 days with no human resolution or implementation details, indicating the task was abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | The request to update charmcraft tests to the new craft-application infrastructure was closed and synced to Jira ticket CHARMCRAFT-631 for external tracking and resolution. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed and synced to Jira as CHARMCRAFT-631. No pull request or implementation was submitted, indicating the task was abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed and synced to internal Jira ticket CHARMCRAFT-631. No code changes, merge, or resolution details were recorded. The task appears abandoned or deferred to external tracking. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. The request to adopt craft-application's new testing infrastructure was not addressed. Only an automated Jira sync comment created internal ticket CHARMCRAFT-631. The issue appears abandoned or superseded. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2365 Add test configuration templates for charmcraft | charmcraft | closed | 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. | |
| #1133 Rebase Charmcraft onto craft-application | charmcraft | closed | Closed without resolution or comments, indicating the task was abandoned or superseded. No implementation, merge, or follow-up details were recorded. | |
| #4609 [test] check proposed craft-application feature | snapcraft | closed | Closed without merging after a maintainer confirmed the test run succeeded. The pull request served as a temporary verification step for the craft-application feature branch and was subsequently abandoned. | |
| #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. | |
| #2132 Prototype integration of testing service | charmcraft | open | Maintainer-created task to integrate craft-application's TestingService into Charmcraft for multi-platform artifact testing. Feature still unimplemented; upstream TestingService with multi-artifact support now exists in craft-application. | |
| #160 Have a way for charmcraft to run the tests | charmcraft | closed | 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. |