Race Condition Check: spec/system/case_contacts/#6785
Open
stefannibrasil wants to merge 1 commit intorubyforgood:mainfrom
Open
Race Condition Check: spec/system/case_contacts/#6785stefannibrasil wants to merge 1 commit intorubyforgood:mainfrom
stefannibrasil wants to merge 1 commit intorubyforgood:mainfrom
Conversation
stefannibrasil
commented
Mar 18, 2026
| let!(:case_assignment) { create(:case_assignment, volunteer: volunteer, casa_case: casa_case) } | ||
|
|
||
| context "without filter" do | ||
| let(:case_contacts) do |
Contributor
Author
There was a problem hiding this comment.
Instead of creating 4 factories for all scenarios, only create the necessary ones for each scenario.
Resolves rubyforgood#6701 When github's free CI servers are under heavy load, a race condition between the page loading and checking the database causes tests to flake. This is caused by a system test inputting data into a form then immediately checking the database without waiting for the form to finish submitting. For every database check in the system files, this ensures it's preceded by a capybara matcher with automatic waiting, such as checking for assertions after the page loads before checking for DB values, or replaced the database check with a check for something to appear on the page. I also took the opportunity to refactor some small things to save up test setup time: - build factories instead of creating as much as possible - require `:js` only when necessary - remove unused variables and factories - keep necessary factories close to where they are used to avoid creating extra factories when not needed - update Date string to Date objects (these were flaky locally), similar to rubyforgood#6764
stefannibrasil
force-pushed
the
sb-case-contacts-6701
branch
from
8f80e41 to
a99b66f
Compare
stefannibrasil
requested review from
FireLemons,
compwron and
elasticspoon
as code owners
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What github issue is this PR for, if any?
Resolves #6701
What changed, and why?
When github's free CI servers are under heavy load, a race condition between the page loading and checking the database causes tests to flake. This is caused by a system test inputting data into a form then immediately checking the database without waiting for the form to finish submitting.
For every database check in the system files, this ensures it's preceded by a capybara matcher with automatic waiting, such as checking for assertions after the page loads before checking for DB values, or replaced the database
check with a check for something to appear on the page.
I also took the opportunity to refactor some small things to save up test setup time:
:jsonly when necessary