← Back to issue list

Spread test the documentation examples

View original Github issue

Metadata

Project
charmcraft
Number
#1962
Type
issue
State
open
Author
lengau
Labels
Created
Updated
Closed

Current evaluation

Feature request to add spread tests for documentation examples (like Rockcraft) to prevent them from becoming outdated. Open since 2023, no labels/assignees, only a Jira-sync bot comment; no evidence of implementation.

Suggested action: needs triage

Reason: The issue has no labels, no assignee, and the only comment is an autogenerated Jira-sync bot message (CRAFT-3570), so it shows no sign of maintainer triage. It is a legitimate internal feature request from a maintainer (lengau), and while a related commit 'ci(docs): spread test documentation (#2126)' exists, there is no evidence it implemented the requested example-testing, so it should be triaged rather than closed.

Impact: 40 Quick Win: 16.0 Staleness: 75 Complexity: 60 Confidence: 65 Support Request: 0

Issue body

### What needs to get done Create spread tests for the examples in the documentation the way Rockcraft does it. ### Why it needs to get done These could otherwise become outdated.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 40
Quick Win: 16.0
Staleness: 75
Complexity: 60
Confidence: 65
Support Request: 0
needs triage Feature request to add spread tests for documentation examples (like Rockcraft) to prevent them from becoming outdated. Open since 2023, no labels/assignees, only a Jira-sync bot comment; no evidence of implementation.
qwen/qwen3.6-35b-a3b
Staleness: 85
Complexity: 30
Confidence: 80
Support Request: 10
needs triage Request to create spread tests for documentation examples to prevent them from becoming outdated. Currently inactive with no maintainer labels, assignees, or progress since creation.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 20
Confidence: 85
Support Request: 0
needs triage Request to add spread tests for documentation examples to prevent them from becoming outdated. Currently unlabelled, unassigned, and inactive for over 10 months with only an automated Jira sync comment.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 30
Confidence: 75
Support Request: 10
needs triage Task to create spread tests for documentation examples to prevent them from becoming outdated. Currently unlabelled, inactive for over a year, and awaiting maintainer assessment.
qwen3.6-35b-a3b-mtp-q6
Staleness: 75
Complexity: 20
Confidence: 85
Support Request: 0
needs triage Create spread tests for documentation examples to prevent them from becoming outdated. Open and inactive for 304 days, awaiting triage and assignment. Synced to Jira CRAFT-3570.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/charmcraft#2126 (confidence 55%)

    Commit f1b73a6e 'ci(docs): spread test documentation (#2126)' suggests docs-related spread CI work, but it is unclear whether it covers the documentation examples requested here.

Related issues

Issue Project State Summary Similarity
#839 Spread tests for documentation examples craft-parts open Feature request to add spread tests for documentation examples (like Rockcraft has). Open 721 days, no labels/assignee/comments, last activity 538 days ago. Pytest ignores tests/spread but no spread tests exist yet.
88%
#665 create new Spread task for daily compatibility matrix testing rockcraft open Feature request to add a dedicated daily spread test that runs rockcraft pack across multiple LXD/multipass/docker versions to catch dependency breakage early. Maintainer discussion on 2024-08-08; no implementation found in current codebase.
72%
#63 spread: add some basic docs on running spread rockcraft merged Added basic documentation for running spread tests, outlining requirements like git submodules, rockcraft snap, and snapd-spread access. Approved by one reviewer and merged with 34 lines added to a single file.
72%
#371 Add a spread test for build-secrets rockcraft open Task to add a spread test verifying build-secrets support in rockcraft. Blocked by craft-application#100, which is now resolved. No labels, no comments, no progress in ~3 years despite active project.
71%
#651 Spread should run the doc tests with a nonroot user rockcraft open Request to run Spread doc tests as a nonroot user to catch permission-related documentation issues (e.g. #649). Open 768 days, last activity 263 days ago, 0 comments, labeled Type: Documentation, authored by a maintainer. No evidence of implementation yet.
71%
#291 Refactor spread testing to use spread extensions fetch-service closed Abandoned. The request to refactor spread testing was synced to internal Jira ticket CRAFT-3690 and closed without implementation. No code changes or resolution were provided.
70%