MushroomObserver / mushroom-observer / 27491230200
98%
main: 98%

LAST BUILD BRANCH: 3745-import-from-user-supplied-url
DEFAULT BRANCH: main
Ran
Jobs 1
Files 1539
Run time 2min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 97.693%. Remained the same
27491230200

push

github

nimmolo 
test infra: parallel system tests + per-worker Capybara port

Two related fixes so `bin/rails test test/system/` can run multi-
worker against the Google Maps API key's referer whitelist.

1. `test/test_helper.rb` — the global
   `parallelize(workers: :number_of_processors)` ignores
   `ENV["PARALLEL_WORKERS"]`. Honor the env var now, falling back to
   `:number_of_processors` when unset.

2. `test/application_system_test_case.rb`:
   - Cap system-test workers at 4 via
     `parallelize(workers: MAPS_API_PORT_COUNT)`, overriding the
     parent. Matches the Google Maps API key's HTTP-Referer
     whitelist (`http://localhost:3000-3003/*`); bump the constant
     when Cloud Console widens the range.
   - Map worker id to its own whitelisted port:
     `Capybara.server_port = 3000 + ENV["TEST_ENV_NUMBER"].to_i`.
     Serial runs leave `TEST_ENV_NUMBER` unset → port 3000.

Verified locally: `bin/rails test test/system/` now spawns 4
workers (Unit Tests-0..3) instead of 12, each binding its own
port. Without these fixes, the parallel run produced 56 errors in
~8 seconds (every worker tried to bind 3000 → 11 of 12 failed
with `Errno::EADDRINUSE`).

Followup: 10 Maps-themed tests still fail under parallel because
Joe's whitelist on 3001-3003 isn't propagated yet (confirmed by
running one Maps test with `TEST_ENV_NUMBER=1` → fails on port
3001, passes on 3000). Once the whitelist lands, parallel runs
should be clean. Test infra is unblocked.

46756 of 47860 relevant lines covered (97.69%)

704.16 hits per line

Jobs
ID Job ID Ran Files Coverage
1 27491230200.1 1539
97.69
 GitHub Action Run
Source Files on build 27491230200