tests: run the master tests against the staging server
Metadata
Current evaluation
Merged changes to configure Travis CI to run master branch tests against the staging server via the TEST_STORE variable, while personal forks use fake servers. Reviewers discussed CI failure notification settings during approval.
Suggested action: —
No scores available.
Issue body
I added TEST_STORE=staging to the travis dashboard. This variable will only
be used by branches from the snapcore organization. So when travis runs the
tests after a branch has landed, it will use the staging server. All the
pull requests coming from personal branches will run the tests against the
fake servers.
LP: [#1668717](https://bugs.launchpad.net/snapcraft/+bug/1668717)
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Merged changes to configure Travis CI to run master branch tests against the staging server via the TEST_STORE variable, while personal forks use fake servers. Reviewers discussed CI failure notification settings during approval. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged. Configures Travis CI to run master branch tests against the staging server via TEST_STORE=staging, while personal branches use fake servers. Contributors discussed routing CI failure alerts to Rocket Chat. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged. Configured Travis CI to run master branch tests against the staging server using the TEST_STORE variable, while personal PRs continue using fake servers. The team also discussed routing CI failure notifications to the snapcraft team. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #602 Add a travis suite to run the staging store tests | snapcraft | merged | Merged. Added Travis CI suite for staging store tests. Known race condition causes occasional registration failures, mitigated by retriggering. Rate limiting and test refactoring planned for production rollout. | |
| #1596072 travis integration tests are not running against the staging store | snapcraft (launchpad) | closed | Abandoned. Closed without action. The proposed Travis CI staging store integration tests were not implemented or tracked further. | |
| #1318 tests: refactor the travis jobs using stages | snapcraft | merged | Merged refactoring of Travis CI jobs to use stages. Approved by two reviewers, the update modifies seven files with 201 additions and 40 deletions to streamline the test pipeline. | |
| #603 Run the travis tests on the ubuntu-core team against the staging store | snapcraft | closed | Closed without merging as a demonstration PR to verify that PR #602 works for personal branches using the fake store. The author explicitly requested not to merge, so it was abandoned after validating the CI behavior. | |
| #601 Add a travis suite to run the staging store tests | snapcraft | closed | Abandoned and closed by the author, who realized the branch was personal and required testing on an ubuntu-core branch instead. The Travis CI suite addition was not merged. | |
| #3090 ci: move staging store tests to spread | snapcraft | merged | Merged into master. The change migrated staging store tests to the spread testing framework, removing 1434 lines across 27 files. Approved by two reviewers, passed CI, and achieved 100% diff coverage prior to integration. | |
| #2903 tests: fix status test for staging store | snapcraft | merged | Merged into master after approval and passing CI. The change corrected the staging store status test with a five-line update across one file, resulting in negligible coverage impact. |