Make turbo_test.rb
consistent with Rails' generated test_helper.rb
#328
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.
I've opened this as a draft PR, since I'm unsure about the root-cause of database records leaking across test runs
As a follow-up to the short-term solution shipped in
hotwired/turbo-rails#248, this commit attempts to make the
test/turbo_test.rb
file's setup consistent with the test harness setupgenerated by Rails' engine generator code.
To that end, this commit:
test/turbo_test.rb
file totest/test_helper.rb
require
calls for particular dependencies../test/dummy/config/environment
file is required ahead of therails/test_help
file