CodeForPhilly / CodeForPhilly/benefit-decision-toolkit
Use the new "run-all-tests" wrapper in CI/CD
- Dominant language
- Java
- Stars
- 15
- Forks
- 5
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 23
Description
Relates to #417
we should be able to simplify CI by using the wrapper in one GH action instead of multiple GH actions for the variety of tests.
why? so that we run the same tests all the way through the process
Possible downside: might be slower on average because the `run-all-tests` script (aka `devbox run test`) doesn't run the suites in parallel.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the existing GitHub Actions and the run-all-tests entry point, also invoked as `devbox run test`. Replace the multiple test actions with one action using that wrapper, then verify that the same test suites run through CI and compare the resulting runtime.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, testing
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100