feat(testing): execute spread on generated file
Metadata
Current evaluation
Merged #592: the test command now resolves the backend, writes a temporary spread.yaml, and executes Spread against the generated file.
Resolution: closed resolved
Reason: PR #592 was approved and merged, completing the generated-spread-file workflow. PR #595 separately fixed an unrelated integration-test failure caused by external changes.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Process the craft test spread.yaml file and generate a temporary
file with resolved testing backend. Execute spread on the generated
file.
- [ ] Have you followed the guidelines for contributing?
- [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [ ] Have you successfully run `tox`?
-----
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged #592: the test command now resolves the backend, writes a temporary spread.yaml, and executes Spread against the generated file. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged canonical/craft-application#592, making testing resolve the backend, generate a temporary spread file, and run spread against it. Follow-up #595 fixed an integration-test incompatibility. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged canonical/craft-application#592: testing now resolves the backend, generates a temporary spread file, and executes spread against it. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged after approval. Updates the testing workflow to execute spread on a generated temporary file with a resolved testing backend. Unrelated integration test failures were addressed in a separate pull request. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/craft-application#595
(confidence 100%)
Merged follow-up fixing a separate broken integration test, not the feature itself.
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. | |
| #723 fix(testing): more intelligent test handling | craft-application | merged | Merged PR #723 via commit 6b319b77, running Spread tests as root and strictly validating only top-level spread.yaml keys. | |
| #565 feat(testing): process simplified spread.yaml | craft-application | merged | Merged PR #565 added simplified spread.yaml expansion into a complete project file, resolving #560 after approval by two reviewers. | |
| #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. | |
| #1374 tests: set up the spread execution in linode | snapcraft | merged | Merged PR #1374 (commit a34bb1ca8) set up Spread test execution on Linode across six files after two approvals. | |
| #1514 feat(testing): add spread testing template files | charmcraft | closed | Closed unmerged as superseded by #1660 (commit 097a4e9a), which added charmcraft test and Spread templates, plus merged follow-up #1686 (58d36668). |