diff options
| author | yuuji.yaginuma <yuuji.yaginuma@gmail.com> | 2017-06-03 14:00:25 +0900 |
|---|---|---|
| committer | yuuji.yaginuma <yuuji.yaginuma@gmail.com> | 2017-06-03 18:28:14 +0900 |
| commit | cd64345812567cf67fc7cca740ffc211b272e9f1 (patch) | |
| tree | 1c2212984e9c37cc3a5ad45f29e808c85c5c06da /railties/test/commands | |
| parent | 88ae9bf174d583153dfd93cfe3b916dfcdd16413 (diff) | |
| download | rails-cd64345812567cf67fc7cca740ffc211b272e9f1.tar.gz rails-cd64345812567cf67fc7cca740ffc211b272e9f1.tar.bz2 rails-cd64345812567cf67fc7cca740ffc211b272e9f1.zip | |
Explicitly clear type map before run `test_only_reload_type_map_once_for_every_unknown_type`
Currently, the following test fails.
```
bin/test -a sqlite3_mem --seed 37473 test/cases/relation_test.rb
```
This is due to reset connection in `test_respond_to_for_non_selected_element` postprocessing.
This reset is added with #29332 for `test_only_reload_type_map_once_for_every_unknown_type`.
Since the above test expects the type map to be empty at the time of
test run, I think that it is better to empty the type map before test run.
Diffstat (limited to 'railties/test/commands')
0 files changed, 0 insertions, 0 deletions