Relax assertions in connection config tests #32674
Merged
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.
At the moment these two ActiveRecord tests pass with
rake test:sqlite3
,but fail with
ARCONN=sqlite3 bin/test
.Rails.root
is defined when runningbin/test
, but not when runningthe rake task. When
Rails.root
is defined,config[:database]
willlook something like
vagrant/rails/activerecord/db/primary.sqlite3
instead of just
db/primary.sqlite3
.rails/activerecord/lib/active_record/connection_adapters/sqlite3_adapter.rb
Line 27 in 00caf95
Relaxing
assert_equal
toassert_match
will allow these tests to passregardless of how they are run.
I do have a question why we need both ways to run tests. I have been
using
bin/test
lately, but I see from #32426 that this is not the preferredmethod.