← Back to issue list

Prototype integration of testing service

View original Github issue

Metadata

Project
charmcraft
Number
#2132
Type
issue
State
open
Author
cmatsuoka
Labels
—
Created
Updated
Closed
—

Current evaluation

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.

Suggested action: keep open

Reason: Created by maintainer cmatsuoka as a scoped task; charmcraft/services/__init__.py still has no 'testing' entry, confirming the feature is unimplemented. Upstream craft-application now ships TestingService with multi-artifact support (PR #1167), making this more actionable than at creation. No labels or assignee, but the task remains relevant and closing would lose tracking of a known gap.

Impact: 65 Quick Win: 16.25 Staleness: 65 Complexity: 75 Confidence: 75 Support Request: 0

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
qwen/qwen3.8-27b
Impact: 65
Quick Win: 16.25
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.
qwen3.6-35b-a3b-mtp-q6
Staleness: 75
Complexity: 60
Confidence: 75
Support Request: 0
needs triage Integrate testing service into Charmcraft for multi-platform artifact testing, potentially requiring craft-application refactoring. Stale for 304 days; synced to Jira CRAFT-4073 and awaiting implementation.

Update history

No update history recorded yet.

Related work

  • Blocked By: canonical/craft-application#1167 (confidence 80%)

    craft-application PR 'feat: support testing of multi-artifact projects' provides the upstream multi-artifact testing capability this task depends on; now merged.

  • Related To: canonical/craft-application#694 (confidence 75%)

    Original PR adding TestingService and test command to craft-application, the foundation this integration builds upon.

Related issues

Issue Project State Summary Similarity
#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.
70%