diff options
| author | Yves Senn <yves.senn@gmail.com> | 2014-11-24 12:04:01 +0100 |
|---|---|---|
| committer | Yves Senn <yves.senn@gmail.com> | 2014-11-25 18:17:01 +0100 |
| commit | 5c4495538bb4e8808ce077f08ea6b809952daa44 (patch) | |
| tree | ffbe61d499b774bc9c5cc939225a1f55564cdb99 /actionview/lib/action_view.rb | |
| parent | 9e9793b440c044b765f2d1f702feeb92aef2b139 (diff) | |
| download | rails-5c4495538bb4e8808ce077f08ea6b809952daa44.tar.gz rails-5c4495538bb4e8808ce077f08ea6b809952daa44.tar.bz2 rails-5c4495538bb4e8808ce077f08ea6b809952daa44.zip | |
bring back `db:test:prepare`.
This reverts deprecations added in #13528.
The task is brought back for two reasons:
1. Give plugins a way to hook into the test database initialization process
2. Give the user a way to force a test database synchronization
While `test:prepare` is still a dependency of every test task, `db:test:prepare`
no longer hooks into it. This means that `test:prepare` runs before the schema
is synchronized. Plugins, which insert data can now hook into `db:test:prepare`.
The automatic schema maintenance can't detect when a migration is rolled-back,
modified and reapplied. In this case the user has to fall back to `db:test:prepare`
to force the synchronization to happen.
Diffstat (limited to 'actionview/lib/action_view.rb')
0 files changed, 0 insertions, 0 deletions