Prototype integration of testing service
Metadata
Current evaluation
Feature request to integrate craft-application's testing service into charmcraft, including a strategy for testing multi-platform artefacts. Still unimplemented; no labels or maintainer triage in GitHub, Jira ticket CRAFT-4073 created.
Suggested action: needs triage
Reason: The issue has no labels, assignee, or maintainer comments — only an automated Jira sync comment (CRAFT-4073). I verified the testing service is still absent from charmcraft's service registry (charmcraft/services/__init__.py) and no charmcraft commits reference TestingService, so the feature remains unimplemented and has not been triaged in GitHub.
Evaluated by: mr-cal-bot
Impact:
60
Quick Win:
5
Complexity:
80
Confidence:
65
Actionability:
45
Issue body
### What needs to get done
Add support for the testing service in Charmcraft. Determine the best strategy to test multi-platform artefacts: this is different from snapcraft where a single artifact is tested in multiple systems, in Charmcraft each artefact is tested on a single system and possibly a single testing run must happen after all artefacts are generated.
This task may involve refactoring of the testing infrastructure in craft-application to accomodate special needs of multi-platform testing.
### Why it needs to get done
Charmcraft testing support is long overdue. Previous testing experiments were not approved and must be replaced with this new design.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| ~deepseek/deepseek-pro-latest |
Impact:
60
Quick Win:
5
Complexity:
80
Confidence:
65
Actionability:
45
|
needs triage | Feature request to integrate craft-application's testing service into charmcraft, including a strategy for testing multi-platform artefacts. Still unimplemented; no labels or maintainer triage in GitHub, Jira ticket CRAFT-4073 created. | |
| stealth/space-bunny-alpha |
Impact:
64
Quick Win:
5
Complexity:
84
Confidence:
90
Actionability:
52
|
needs triage | Multi-platform testing-service integration remains an unlabelled design task; the only follow-up is an automated CRAFT-4073 sync, with no implementation or triage decision recorded. | |
| qwen/qwen3.6-35b-a3b |
Impact:
65
Quick Win:
13
Complexity:
65
Confidence:
70
Actionability:
55
|
needs triage | Feature request to prototype testing service integration in Charmcraft with multi-platform artifact testing strategy. Open 594 days, last activity 398 days ago, no labels or maintainer assessment. | |
| qwen/qwen3.8-27b |
Impact:
65
Quick Win:
16
Staleness:
65
Complexity:
75
Confidence:
75
Support Request:
0
|
keep 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. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
90
Complexity:
70
Confidence:
80
Support Request:
10
|
close stale | Prototype task to integrate a testing service into Charmcraft, addressing multi-platform artifact testing and potential craft-application refactoring. Currently unlabelled and inactive for over a year. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
90
Complexity:
75
Confidence:
85
Support Request:
5
|
close stale | Prototype task for integrating a testing service into Charmcraft. Open for 17 months with no maintainer engagement beyond an automated Jira sync. Lacks current relevance or active development. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
80
Complexity:
70
Confidence:
75
Support Request:
5
|
needs triage | Prototype task to integrate a testing service into Charmcraft for multi-platform artifact testing. Currently unlabelled and untriaged after 17 months. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.