Start using `spread` for integration tests
Metadata
Current evaluation
Completed and merged via pull request #862, which implemented the spread infrastructure and added integration tests. The issue was closed after the changes were successfully integrated.
Suggested action: —
No scores available.
Issue body
After the initial infrastructure is added/setup, we can start actually adding integration tests.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen3.6-35b-a3b-mtp-q6 | — | — | Completed and merged via pull request #862, which implemented the spread infrastructure and added integration tests. The issue was closed after the changes were successfully integrated. | |
| qwen/qwen3.6-35b-a3b | — | — | Resolved via pull request #862. The spread integration test infrastructure was implemented, fulfilling the request to adopt spread for testing. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Integration tests using spread were implemented and merged in pull request #862, resolving the request to adopt spread for testing. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Resolved via pull request 862. The spread testing framework was integrated to run integration tests, completing the requested infrastructure setup. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2173 tests: create basic integration test spread infrastructure | snapcraft | merged | Merged changes establishing basic integration test infrastructure using Spread. Resolves LP: #1779419 by implementing a reusable test suite, initially proven with the Go plugin test. Approved after iterative revisions. | |
| #706 Add integration tests using the snap | charmcraft | closed | Resolved by implementing the requested snap integration tests as part of the spread test suite. | |
| #592 feat(testing): execute spread on generated file | craft-application | merged | 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. | |
| #1783825 Move Autotools plugin tests to spread | snapcraft (launchpad) | closed | Autotools plugin integration tests were migrated to a Spread suite to improve parallelization and cross-system compatibility. The change was implemented and the issue closed. | |
| #4248 spread: separate legacy tests | snapcraft | closed | Merged into main. The pull request separated legacy spread tests into dedicated GitHub Actions workflows to reduce redundant CI execution time and improve pipeline efficiency. | |
| #430 Improve integration tests | craft-providers | open | Enhancement proposal to restructure integration tests, either by migrating to spread or reorganizing existing tests to address disk space exhaustion on GitHub runners. | |
| #1555 refactor(tests/spread): stop use init in most spread tests | charmcraft | closed | Author closed and abandoned the changes after self-review deemed the approach flawed. No code was merged or reviewed. | |
| #613 Execute spread testing | craft-application | closed | Implemented a service to execute spread tests for craft projects. The feature was completed and merged via pull request #694 in the canonical/craft-application repository. | |
| #9 lint spread tests with shellcheck | snapcraft-rocks | closed | Shellcheck linting for spread tests was implemented via merged pull request #14. The issue is closed. | |
| #1287 tests: minor cleanups on the spread tests | snapcraft | merged | Merged minor spread test cleanups into master. Modified four files with 16 additions and 6 deletions. Approved by one reviewer with zero unresolved comments, maintaining 95.27% coverage upon integration. |