posit-dev / posit-dev/images-shared
Optimize bakery's testing
Open
Nobody has claimed this yet.
cicd
cvp:0
docker
priority/medium
python
qa
tdp:2
tech debt
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 22
Description
We recently had to push the test job to using ubuntu-latest-4x runners after adding tests that involved building a multidimensional matrix. Tests are now pushing the 20min mark so it may be time to consider going back and streamlining/optimizing our testing to ensure testing feedback is quick and actionable.
Some options to consider:
- Avoid invoking Docker and builds where possible and mocking those interactions for unit tests.
- Split "end-to-end" or "integration" type tests into a separate job so feedback from unit tests can be quicker while still allowing for longer tests to act.
- Use more "no-op" type
Containerfiledefinitions if we are building artifacts where possible rather than truly building out images. - Ensure that any images we do have to build are cleaned up immediately during teardown of the test that invoked them.
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
The issue names no files, tests, or entry points. Start by locating the test job and its multidimensional matrix configuration, then measure where Docker builds and integration tests consume time; done means faster, actionable unit-test feedback while longer tests remain covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, python
- Domain
- ci-cd, devops, testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100