tests: add spread tests for registries
Metadata
Current evaluation
Added spread tests for edit-registries and list-registries, resolving issue #5054. Merged following approval by two reviewers. Minor unrelated network failures were noted but did not block the merge.
Suggested action: —
No scores available.
Issue body
- [x] Have you followed the [guidelines for contributing](https://github.com/canonical/snapcraft/blob/main/CONTRIBUTING.md)?
- [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [x] Have you successfully run `tox run -m lint`?
- [x] Have you successfully run `tox run -e test-py310`? (supported versions: `py39`, `py310`, `py311`, `py312`)
-----
Add a spread test for `edit-registries` and `list-registries`.
Fixes #5054
(CRAFT-3419)
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Added spread tests for edit-registries and list-registries, resolving issue #5054. Merged following approval by two reviewers. Minor unrelated network failures were noted but did not block the merge. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged changes adding spread tests for edit-registries and list-registries, resolving issue #5054. Initial test failures were unrelated network errors. The updates passed all checks and were successfully integrated. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged to add spread tests for edit-registries and list-registries. Closes #5054. Early test failures stemmed from unrelated network issues and did not prevent integration. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4924 tests: add spread tests for validation-sets | snapcraft | merged | Merged changes adding spread tests for edit-validation-sets and list-validation-sets. Approved by two reviewers with passing CI, resolving issue #4918. | |
| #5054 Add a spread test for registries | snapcraft | closed | Closed without implementation. The request to add a spread test for registries was abandoned, with no pull request or resolution documented beyond an automated Jira sync comment. | |
| #5072 feat: build, sign and publish registries | snapcraft | merged | Merged. Finalizes the edit-registries command by adding build, sign, and publish capabilities for registries, resolving #5018. Approved by two reviewers, passed CI, and spanned 11 files. Spread tests deferred to a separate PR. | |
| #1290 test(spread): clean up store tests | charmcraft | merged | Merged cleanup of spread store tests, removing 28 lines across four files. The underlying library test failure is fixed in PR #1292. Approved by two reviewers. | |
| #13 test(spread): add more spread tests | snapcraft-rocks | merged | Successfully merged spread tests covering architectures, chisel slices, craftctl, package-repositories, and patchelf. Approved by two reviewers across 15 files (+206/-5 lines). | |
| #4433 tests(spread): add remote-build spread test | snapcraft | merged | Merged changes adding spread tests for new and legacy remote-build, resolving issue #4398. Approved by two reviewers with passing CI checks. | |
| #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. | |
| #534 test(spread): workaround for flaky test | fetch-service | merged | Merged a workaround for a flaky spread test (issue #533). The change adjusts one file (+2/-1 lines) to skip a no-op name query check while retaining other validations. Approved by two reviewers and passed all CI checks. | |
| #3663 tests: update spread url | snapcraft | merged | Merged following reviewer approval and passing CI. Updated spread tarball URLs in test configuration files, modifying two files with minimal changes. | |
| #3662 tests: update spread url | snapcraft | merged | Merged update to spread tarball URLs in test files. Approved by a reviewer, passed CI checks, modified two files with minimal changes, and maintained existing code coverage. |