Speed up the RSpec suite: parallelize CI, then shrink the JS system-spec slice
Maintainers usually reply within 1 day
@Sufiyan-MSA is already working on this.
Since Sep 11, 2026.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- ci-cd, performance, testing-qa
Research direction
Start with .github/workflows/rspec.yml and compare its current commands with the per-process settings in config/database.yml, config/storage.yml, spec/rails_helper.rb, spec/support/download_helpers.rb, and spec/spec_helper.rb. Run the documented baseline and inspect the SimpleCov and runtime-log handling before choosing a phase. Done means the selected parallelism, balancing, coverage, or spec-speed change works without regressing CI results.
Written by the indexing model from the issue text.
Description
Baseline (measured, not guessed)
The CI rspec step on main takes 8.4 min, in one process, with no parallelism (bundle exec rspec).
Local timings by slice:
| Slice | Examples | Time | Per example |
|---|---|---|---|
spec/system :js |
368 | 498s | 1.35s |
spec/requests |
932 | 50s | 0.05s |
spec/system (rack_test) |
388 | 36s | 0.09s |
spec/models |
666 | 22s | 0.03s |
JS system specs are ~82% of the wall clock for ~16% of the examples, and they ran at 28% CPU — the process sits idle waiting on Chrome. That single fact sets the priority order: parallelize first, then shrink the JS set.
Inside the JS slice:
spec/system/accessibility/axe_spec.rb— 45 examples / 118s (24% of JS time)spec/system/casa_cases/edit_spec.rb— 26 examples / 61sspec/system/typeahead_controls_spec.rb— 1 example / 30sspec/system/layouts/flashes_spec.rb— 4 examples / 18.5s
Two things checked and ruled out as meaningful levers: Prosopite's per-example scan costs only ~4% (measured A/B on spec/models, 28.4s vs 29.7s), and Build App + assets:precompile is 0.2 min. Neither is worth touching early.
Phase 1 — turn on parallelism (config only, no spec edits)
The repo is already fully wired for parallel_tests and just doesn't use it in CI. The gem is in the Gemfile, and every per-process collision point is already parameterized by TEST_ENV_NUMBER:
config/database.yml:17— per-process database nameconfig/storage.yml:3— per-process Active Storage rootspec/rails_helper.rb:132— per-process Capybara server portspec/support/download_helpers.rb:3— per-process download dirspec/spec_helper.rb:18— per-process SimpleCovcommand_name
Someone built this and it fell out of CI. Tasks:
- In
.github/workflows/rspec.yml, replacebundle exec rake db:create db:schema:loadwithbundle exec rake parallel:create parallel:load_schema, andbundle exec rspecwithbundle exec parallel_test spec --type rspec -n 4. - Cache
tmp/parallel_runtime_rspec.logacross runs so--group-by runtimebalances groups. Without it, whichever group holdsaxe_specbecomes the critical path. - Add a SimpleCov merge step — bump
SimpleCov.merge_timeoutand collate the per-process resultsets before theqltyupload, or the reported coverage will silently drop.
ubuntu-latest on a public repo is 4 vCPU. Because the JS specs are browser-wait-bound, 4 processes should scale close to linearly: ~8.4 min → ~3 min. Memory headroom needs a check — 4 concurrent headless Chromes in 16 GB should be fine, but watch it.
Phase 2 — shrink the JS slice
- Audit the
:jstags. 368 JS examples is far more than a Hotwire app of this size needs. Every one converted torack_testgoes 1.35s → 0.09s (15×). Highest-yield item on the list, but it's per-file judgment work, so no payoff number until the audit is done. - Move
spec/system/accessibility/axe_spec.rbinto its own CI job. 118s of full page-load + axe-core runs, independent of everything else. Running it concurrently takes ~2 min off the critical path at zero risk. - Fix the flakes, then cut
retry: 3.spec/support/rspec_retry.rbretries every:jsexample up to 3× in CI, so the slowest specs are also the ones that can triple in cost.spec/system/learning_hours/date_range_spec.rbfailed 3 examples in a local run and is burning retries in CI right now. Fix it, then drop toretry: 1. - Fix
spec/system/typeahead_controls_spec.rb. One example, 30s, ~20let!records, two explicitsleeps and aTimeout.timeout(6)poll loop. Split it per control and replace the manual polling with Capybara's own waiting.
Phase 3 — keep it from regressing
- Add
config.profile_examples = 10behind an env var so the next slow spec is visible without a manual profiling run. - Set
.prosopite_ignoredirectories to:offrather than:log_only.spec/systemis on that list, so its N+1s can never fail the build, yet the slowest 82% of the suite still pays the scan cost. Only worth ~4% though — do it last.
- Dominant language
- Ruby
- Stars
- 384
- Forks
- 558
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 63
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from rubyforgood/casa
-
⛓️ Security Difficulty: Easy Good First Issue Help Wanted ruby Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
rubyforgood/casa#7404 ·
Maintainers usually reply within 1 day
-
Difficulty: Easy Good First Issue Help Wanted ruby Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
rubyforgood/casa#7402 ·
Maintainers usually reply within 1 day
-
Remove the bin/bundle binstub (Heroku warns it can break Bundler on deploy)Possibly taken @Akash-Dhanwate claimed this 8 days ago. Opendependencies Difficulty: Easy Good First Issue
Difficulty 1/5 Under an hour Newbie friendliness 82/100
rubyforgood/casa#7325 · 2 comments ·
Maintainers usually reply within 1 day
-
Reports page: move export-button disable/re-enable into a Stimulus controllerMay be free again @Akash-Dhanwate claimed this 9 days ago, and no pull request is open. OpenDifficulty: Easy Good First Issue Help Wanted javascript
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rubyforgood/casa#7311 · 2 comments ·
Maintainers usually reply within 1 day
-
New case: use Stimulus for the "I don't know the court date yet" toggleMay be free again @Aryankn29 claimed this 9 days ago, and no pull request is open. OpenDifficulty: Easy Good First Issue Help Wanted javascript
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
rubyforgood/casa#7310 · 1 comment ·
Maintainers usually reply within 1 day
All issues in rubyforgood/casa
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
internetee/registry#2984 ·
Maintainers usually reply within 6 days
-
Redis Lua error `@user_script:52: ERR value is not an integer or out of range` when `window_size` is configuredPossibly taken @mimosa claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
riscv/riscv-unified-db#2829 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
docker-library/ruby#534 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100