Spread test the documentation examples
Metadata
Current evaluation
Documentation examples are now covered by dedicated Spread tests and CI through merged PR #2126; the still-open issue should be closed.
Suggested action: close resolved
Reason: Merged PR #2126, commit f1b73a6e, added documentation Spread tests and CI. The current .github/workflows/spread-docs.yaml still selects systems under ci:docs/ and runs those tests, confirming the requested coverage remains implemented.
Evaluated by: mr-cal-bot
Impact:
45
Quick Win:
27
Complexity:
38
Confidence:
99
Actionability:
95
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 |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
45
Quick Win:
27
Complexity:
38
Confidence:
99
Actionability:
95
|
close resolved | Documentation examples are now covered by dedicated Spread tests and CI through merged PR #2126; the still-open issue should be closed. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
14
Complexity:
40
Confidence:
80
Actionability:
80
|
close resolved | Request to create spread tests for documentation examples to prevent them from becoming outdated. Likely resolved by PR #2126. | |
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
16
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. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
charmcraft#2126
(confidence 99%)
Merged commit f1b73a6e added CI for documentation Spread tests and adapted the tasks for hosted runners.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #613 Execute spread testing | craft-application | closed | Spread testing delivered: TestingService and an opt-in 'test' command merged via PR #694 (commit 4910b2d8), building on #565 and #592. Maintainer mr-cal closed the issue citing that PR. | |
| #2126 ci(docs): spread test documentation | charmcraft | merged | Merged PR #2126 in commit f1b73a6e, adding CI for documentation spread tests and adapting spread tasks for Google-hosted runners. | |
| #2029 Run documentation spread tests in CI | charmcraft | closed | Documentation spread tests were enabled in CI by merged PR #2126 (commit f1b73a6e), adding the docs spread workflow and fixes for Google-hosted runners. | |
| #143 docs: make docs spread-testable | craft-store | merged | Merged PR #143 as commit 1676433, adding infrastructure to manually spread-test the restructured documentation without running docs spread tests in CI. | |
| #926 test: address a couple of non-flaky spread failures | rockcraft | merged | Merged PR #926 updated three spread-test configuration files to address persistent failures; all CI checks passed and two reviewers approved. | |
| #839 Spread tests for documentation examples | craft-parts | open | Maintainer request (lengau) to add spread tests for craft-parts docs examples like Rockcraft has; still open and unimplemented — only the hello-craft-parts tutorial has a spread-ready task.yaml. | |
| #6202 test(spread): create core26 spread test suite | snapcraft | merged | Merged PR #6202 as a9a5b4750, adding core26 Spread tests and CI coverage while generalizing common tests for core22, core24, and core26. | |
| #665 Start using `spread` for integration tests | charmcraft | closed | Adopted spread for integration tests via merged PR canonical/charmcraft#862 (merge commit 7790c044, branch spread-bootstrap). Issue closed by maintainer sergiusens on 2023-03-16 noting the work was done in that PR. | |
| #2276 spread: move legacy wiki tests to spread | snapcraft | merged | Merged PR #2276 as commit 806b0b0db, moving all non-fake-server legacy wiki tests from the general integration suite to Spread. | |
| #291 Refactor spread testing to use spread extensions | fetch-service | closed | Fixed by merged PR #299 (commit 44d9906), which refactored spread tests to generate spread.yaml and use the new spread extension framework. |