aboutsummaryrefslogtreecommitdiffstats
path: root/activerecord
diff options
context:
space:
mode:
authorSean Griffin <sean@seantheprogrammer.com>2015-12-16 15:17:36 -0700
committerSean Griffin <sean@seantheprogrammer.com>2015-12-16 15:17:36 -0700
commit7fb47a8559db34e923ab4971768260757429c445 (patch)
tree509ce3e534f4e8c10d2ee8bd889356ef5a6ccca7 /activerecord
parentf39aa4dd3995a9d11b426af7f12841d515673a4c (diff)
downloadrails-7fb47a8559db34e923ab4971768260757429c445.tar.gz
rails-7fb47a8559db34e923ab4971768260757429c445.tar.bz2
rails-7fb47a8559db34e923ab4971768260757429c445.zip
Don't over-specify types in our tests
This test was failing when run on Windows using PostgreSQL. Depending on the OS (and 32 vs 64 bit), this type could be a `BigNum`. We could loosen the assertion to `Numeric`, but if the value is equal to the expected, and responds to `bitlength` properly, who cares?
Diffstat (limited to 'activerecord')
-rw-r--r--activerecord/test/cases/migration_test.rb1
1 files changed, 0 insertions, 1 deletions
diff --git a/activerecord/test/cases/migration_test.rb b/activerecord/test/cases/migration_test.rb
index 19be357b6e..b6813891c6 100644
--- a/activerecord/test/cases/migration_test.rb
+++ b/activerecord/test/cases/migration_test.rb
@@ -549,7 +549,6 @@ class MigrationTest < ActiveRecord::TestCase
expected_id = Zlib.crc32(current_database) * salt
assert lock_id == expected_id, "expected lock id generated by the migrator to be #{expected_id}, but it was #{lock_id} instead"
- assert lock_id.is_a?(Fixnum), "expected lock id to be a Fixnum, but it wasn't"
assert lock_id.bit_length <= 63, "lock id must be a signed integer of max 63 bits magnitude"
end