mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
becf1bcb1d
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. |
||
|---|---|---|
| .. | ||
| application | ||
| commands | ||
| configuration | ||
| fixtures | ||
| generators | ||
| isolation | ||
| railties | ||
| test_unit | ||
| abstract_unit.rb | ||
| app_loader_test.rb | ||
| backtrace_cleaner_test.rb | ||
| code_statistics_calculator_test.rb | ||
| code_statistics_test.rb | ||
| engine_test.rb | ||
| env_helpers.rb | ||
| generators_test.rb | ||
| initializable_test.rb | ||
| path_generation_test.rb | ||
| paths_test.rb | ||
| rack_logger_test.rb | ||
| rails_info_controller_test.rb | ||
| rails_info_test.rb | ||
| version_test.rb | ||