diff options
| author | eileencodes <eileencodes@gmail.com> | 2015-12-15 13:56:47 -0500 |
|---|---|---|
| committer | eileencodes <eileencodes@gmail.com> | 2015-12-15 15:19:26 -0500 |
| commit | becf1bcb1d6e72e782995507ebc89d75db357184 (patch) | |
| tree | 412ef453bab51877b3b5f0847f8904af3be614e1 /.yardopts | |
| parent | 98a039dcd987fd3a8c2c0cbd527c71ac3ffaaf06 (diff) | |
| download | rails-becf1bcb1d6e72e782995507ebc89d75db357184.tar.gz rails-becf1bcb1d6e72e782995507ebc89d75db357184.tar.bz2 rails-becf1bcb1d6e72e782995507ebc89d75db357184.zip | |
Run railties generated app tests in test env
Running railties generated app tests in development env can cause unintended
consequences. The environments are different and tests aren't meant to be
run in development mode.
The changes to the generator exposed this issue where the random test
order in the generated apps could cause problems when those tests are
run in development mode.
Particularly we saw failures in `railties/test/application/rake_test.rb`
generated apps that used the scaffold to create applications and then
run the migration and immediately run the tests. The error we saw was
`ActiveRecord::RecordNotFound: Couldn't find User with 'id'=980190962`
and seemed to only occur if the destroy test ran first. I'm not entirely
sure _why_ this causes that error to be thrown but I believe it is
related to the environments being different.
Diffstat (limited to '.yardopts')
0 files changed, 0 insertions, 0 deletions