diff options
| author | Guilherme Mansur <guilherme.mansur@shopify.com> | 2019-04-12 11:42:31 -0400 |
|---|---|---|
| committer | Guilherme Mansur <guilherme.mansur@shopify.com> | 2019-04-12 15:47:54 -0400 |
| commit | cd50e952e29c9824c4d530e99eb81fc1f4be2012 (patch) | |
| tree | 47e2f77f2c623ea105b9d5f9fcce4b5cf85bef4e /actioncable/Rakefile | |
| parent | 713f62430a42294dcb156cc8f38b41509a60d7a6 (diff) | |
| download | rails-cd50e952e29c9824c4d530e99eb81fc1f4be2012.tar.gz rails-cd50e952e29c9824c4d530e99eb81fc1f4be2012.tar.bz2 rails-cd50e952e29c9824c4d530e99eb81fc1f4be2012.zip | |
Fix test flakyness due to `test_truncate_tables`
`Truncate Tables posts` will also reset the `AUTOINCREMENT` this causes
a situation where if a test suite that uses the `taggings` fixtures runs
and subsequently the `test_truncate_tables` run, newly created posts
would reference the `tagging` in the database. This commit resest the
state of the posts table after the `connection.truncate` call in the
`test_truncate_tables`, as well as all other tests that call `trucate`
This ensures the associations and db state remain consistent after the
tests.
Fixes: https://github.com/rails/rails/issues/35941
Diffstat (limited to 'actioncable/Rakefile')
0 files changed, 0 insertions, 0 deletions