rubyforgood / rubyforgood/casa
proposal: Reduce CI runtime by shrinking the docker workflow rspec suite
Open
Nobody has claimed this yet.
no-issue-activity
🧪 Tests
- Dominant language
- Ruby
- Stars
- 381
- Forks
- 542
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 47
Description
What's up?
The docker.yml and rspec.yml workflows both run the whole Rspec test suite, which increases total runtime of the full PR checks list and increases the risk of flaky test failures by 100%.
What are you thinking?
I propose reducing the docker.yml workflow to a single "smoke test" spec run.
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
Start by comparing .github/workflows/docker.yml and .github/workflows/rspec.yml, then inspect how the RSpec suite is invoked in the Docker workflow. Identify a suitable single smoke-test spec and verify that docker.yml runs only it while rspec.yml continues running the full suite; confirm the PR checks complete with reduced runtime.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, ruby
- Domain
- ci-cd, testing-qa
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100