mozilla-services / mozilla-services/syncstorage-rs
Run tokenserver unit tests separately from e2e tests
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.8k
- Forks
- 86
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 21
Description
https://mozilla-hub.atlassian.net/browse/STOR-526 added missing Tokenserver unit tests to CI, however: they run alongside the e2e (integration) tests – meaning their test reports are included in the integration test results file whereas we have separate test metrics for unit tests. So ideally these would run with results in the unit tests bucket.
However we can’t easily accomplish this yet, as they’re still relying on the boto library which is broken on Python > 3.11 (and we’re using 3.12). We get away with running them via compose since the Docker is still on Debian bookworm (which uses Python 3.11).
┆Issue is synchronized with this Jira Task
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the Tokenserver unit-test and e2e/integration-test CI entry points, along with the compose configuration that runs them. First inspect how the boto dependency and Python 3.11/3.12 environments are selected; run the relevant test commands and verify that Tokenserver results are reported in the unit-test bucket rather than the integration results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, python
- Domain
- backend, ci-cd, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100