aboutsummaryrefslogtreecommitdiffstats
path: root/railties/lib/rails/generators/test_unit/system/system_generator.rb
Commit message (Collapse)AuthorAgeFilesLines
* Rename system_test_helper -> application_system_test_caseeileencodes2017-02-201-2/+2
| | | | | | This renames the system test helper file to be application system test case to match what the rest of Rails does. In the future we should consider changing the test_helper to match.
* Refactor config settings to use generated fileeileencodes2017-02-201-1/+5
| | | | | | | | | | | | | | | | | | | Originally I had set up system testing to have one configuration option to be set in the test environment. After thinking it over I think a generated class on app creation would be best. The reason for this is Capybara has a ton of configuration options that I'm sure some folks want to use. Thinking about how we handle screenshots, database transactions, and a whole bunch of other settings it would be better for users to be able to turn all of that on and off. When an app or scaffold is generated a `test/system_test_helper.rb` test helper will be generated as well. This will contain the class for tests to inherit from `ActionSystemTestCase` which will inherit from `ActionSystemTest::Base`. Here is where users can change the test driver, remove the screenshot helper, and add their additional Capybara configuration.
* Appease Rubocopeileencodes2017-02-201-1/+1
| | | | Rubocop / code climate don't like single quotes and prefer doubles.
* Add generators and ability to run system testseileencodes2017-02-201-0/+13
* Generates system test requirements with new Rails app * Includes required default gems in Gemfile for Rails app * Generates a single system test case * Generates a system test case with scaffold