aboutsummaryrefslogtreecommitdiffstats
path: root/railties/test/generators
Commit message (Collapse)AuthorAgeFilesLines
...
| * | Action Cable channel generator should not create JS assets in --api modeRyo Hashimoto2015-12-191-0/+30
| |/
* / display detailed information in inline reportingyuuji.yaginuma2015-12-212-2/+4
|/ | | | | | | | | | | | | | | | | | | | | The errors message only was not displayed, as if it did not use the inline reporting, modified to also information the method name and the like in error are displayed. ``` # before Failed assertion, no message given. bin/rails test test/models/user_test.rb:5 ``` ``` # after Failure: UserTest#test_the_truth: Failed assertion, no message given. bin/rails test test/models/user_test.rb:5 ```
* Do not check the version anymoreRafael Mendonça França2015-12-181-2/+2
| | | | | Our logic is complex now and we don't need to check the version to asset the behavior so I'm removing the checking here.
* Allow normal version updates within a release seriesMatthew Draper2015-12-181-0/+15
| | | | | | | | | | | | | | | | | | | We originally chose to apply very strict versioning on the `rails` entry in the Gemfile, because our future versioning policy was not strongly defined. Now it is, and our policy is very much designed on the expectation that people will regularly update to the latest patch level in their release series... so we should encourage that. Of course, Gemfile.lock will do its job and prevent unplanned updates, just as it does for every other gem in the bundle... but if you run `bundle update`, we want to get you the latest bug/security fixes without requiring a manual edit of the Gemfile entry. Our current version could be a few different shapes, so it takes a bit of work to find the right specifier, but in principle, we match anything of the form x.y.*, where x.y matches our current release series.
* ApplicationMailer should be generated by default just like every other ↵David Heinemeier Hansson2015-12-173-26/+1
| | | | Application* parent
* README.rdoc -> README.md for newly generated pluginsyuuji.yaginuma2015-12-171-3/+3
| | | | I think Markdown is nowadays a better default.
* Fix testsDavid Heinemeier Hansson2015-12-171-2/+0
|
* No longer uses keep now that we have ApplicationRecordDavid Heinemeier Hansson2015-12-161-1/+0
|
* Fix testDavid Heinemeier Hansson2015-12-161-1/+10
|
* Merge branch 'master' into merge-action-cableRafael Mendonça França2015-12-167-26/+37
|\
| * Merge pull request #22567 from gsamokovarov/introduce-application-recordRafael França2015-12-162-0/+12
| |\ | | | | | | Introduce ApplicationRecord, an Active Record layer supertype
| | * Introduce ApplicationRecord, an Active Record layer supertypeGenadi Samokovarov2015-12-162-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It's pretty common for folks to monkey patch `ActiveRecord::Base` to work around an issue or introduce extra functionality. Instead of shoving even more stuff in `ActiveRecord::Base`, `ApplicationRecord` can hold all those custom work the apps may need. Now, we don't wanna encourage all of the application models to inherit from `ActiveRecord::Base`, but we can encourage all the models that do, to inherit from `ApplicationRecord`. Newly generated applications have `app/models/application_record.rb` present by default. The model generators are smart enough to recognize that newly generated models have to inherit from `ApplicationRecord`, but only if it's present.
| * | Update test generators to use ActionDispatch::IntegrationTestAbdelkader Boudih2015-12-154-24/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In Rails 5.1 `ActionController::TestCase` will be moved out of Rails into it's own gem. Please use `ActionDispatch::IntegrationTest` going forward. This changes the generators to use `ActionDispatch::IntegrationTest` and the required URL setup (rather than symbols) for each of the controller actions. Updated fix to #22076.
| * | Do not default to any SerializerSantiago Pastorino2015-12-151-2/+1
| |/ | | | | | | We will wait until 5.1 to make a decision
* | Merge remote-tracking branch 'origin/master' into merge-action-cableRafael Mendonça França2015-12-153-14/+14
|\|
| * Ensure generated migrations include a version numberMatthew Draper2015-12-153-14/+14
| |
* | Add option to skip Action CableRafael Mendonça França2015-12-141-0/+5
|/
* Revert "Merge pull request #22569 from seuros/remove-test-case"eileencodes2015-12-134-12/+12
| | | | | | | | | This reverts commit 9712a7a12b7f9e4dcef751ceda8a73c3f4beb11f, reversing changes made to 3e65c3d3886336e9145438cdeacaf4ebec6a48b8. Reverting because this caused test failures and while we have a followup branch there is still one failure that happens randomly and isn't straight forward to fix.
* Merge pull request #22569 from seuros/remove-test-caseEileen M. Uchitelle2015-12-134-12/+12
|\ | | | | Controller generators should be creating IntegrationTest stubs instea…
| * Controller generators should be creating IntegrationTest stubs instead of ↵Abdelkader Boudih2015-12-134-12/+12
| | | | | | | | ControllerTest
* | Merge pull request #22574 from gsamokovarov/scaffold-500Kasper Timm Hansen2015-12-131-1/+1
|\ \ | | | | | | Prevent a 500 in the default controller scaffold
| * | Prevent a 500 in the default controller scaffoldGenadi Samokovarov2015-12-131-1/+1
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | If you update a record with no attributes, you'll hit a 500 from a guard in `assign_attributes` raising: ```ruby ArgumentError: When assigning attributes, you must pass a hash as an argument. app/controllers/users_controller.rb:44:in `block in update' app/controllers/users_controller.rb:43:in `update' test/controllers/users_controller_test.rb:37:in `block in <class:UsersControllerTest>' ``` Not a biggie, but may be quite confusing for the folks new to the framework.
* / Update web-console to 3.0.0Genadi Samokovarov2015-12-131-2/+2
|/ | | | | Web Console 3.0.0 is compatible with Rails 5, while the 2.x.x releases aren't.
* show relative path the rerun snippet of test runner in rails engineyuuji.yaginuma2015-12-103-22/+58
| | | | | | | | | | | | | Since the absolute path is not required to re-run the test, modified so that unnecessary information is not displayed. ```ruby # before bin/rails test /path/to/blorgh/test/integration/navigation_test.rb:5 # after bin/rails test test/integration/navigation_test.rb:5 ```
* Merge pull request #22508 from ↵Santiago Pastorino2015-12-071-0/+1
|\ | | | | | | | | y-yagi/remove_request_forgery_protection_from_rails_api remove `request_forgery_protection` initializer from rails api
| * remove `request_forgery_protection` initializer from rails apiyuuji.yaginuma2015-12-061-0/+1
| | | | | | | | | | In rails api, since default is so as not to use the `protect_from_forgery`, `request_forgery_protection` initializer I think that's unnecessary
* | Mac OS X use /private as directory to temp fileRafael Mendonça França2015-12-041-1/+1
| | | | | | | | Related with e62ddac05b7d827ae870898d7cd9eaf76e0730aa
* | Remove test_files check from plugin checksRafael Mendonça França2015-12-041-4/+0
|/ | | | Related with 668c006cf33a63ac3f8a8f064c772a339341e70c.
* add `bin/test` script to rails pluginyuuji.yaginuma2015-11-282-1/+129
|
* fix application_controller require_dependency path generated by api scaffold ↵yuuji.yaginuma2015-11-081-0/+24
| | | | | | | | | generator In the app generator, regardless of the namespace, it is adapted to read the same `application_controller.rb`, modified to api generator also be the same behavior. ref 686966a1861e6761021d45f6795de753e8a62216, 06ac63b4c602e4b26cb3bfbf0dfd2bed8b00e786
* Route generator should be idempotent - closes #22082Thiago Pinto2015-10-311-0/+15
|
* Add version constraint to database gem in generated applicationRafael Mendonça França2015-10-291-4/+8
| | | | | | We are using the same version constraint in the database adapters so when a new version of the adapter that doesn't work with the version of rails is released we don't break new applications.
* Use thor class_option to make the primary_key_type option workRafael Mendonça França2015-10-232-6/+10
| | | | Also move the method to the right class
* Move default uuid generation to active_recordJon McCartie2015-10-231-3/+4
|
* remove unnecessary readme in dummy applicationyuuji.yaginuma2015-10-231-0/+13
| | | | `README` it is changed to `README.rdoc` in 6b126e2, it has been changed to` README.md` further 89a12c9.
* Set active_record config for always creating uuids in generatorsJon McCartie2015-10-201-0/+13
|
* Merge pull request #20908 from y-yagi/generate_application_job_inside_engineArthur Nogueira Neves2015-10-131-0/+4
|\ | | | | add application_job.rb to template of mountable engine
| * add application_job.rb to template of mountable engineyuuji.yaginuma2015-07-171-0/+4
| | | | | | | | | | since cb012467214f6e4bb1ac3987554bb75020b4796b, generated job inherents from ApplicationJob, ApplicationJob is required in the mountable engine.
* | do not generate manifest.js in pluginsyuuji.yaginuma2015-10-121-0/+1
| | | | | | | | Since the plugin generator do not generate assets, I think manifest.js also that it unnecessary.
* | Removed Mocha from app generators testsRonak Jangir2015-09-231-87/+106
| |
* | Remove unneeded generator variable.Kasper Timm Hansen2015-09-221-1/+0
| |
* | Removed mocha from Railites PluginGeneratorTestRonak Jangir2015-09-222-15/+35
| |
* | fix application_controller require_dependency path generated by the scaffold ↵yuuji.yaginuma2015-09-201-0/+1
| | | | | | | | | | | | | | generator This is follow up to #6643. In #6643, the controller generator only had been fixed, in this commit to fix the scaffold generator.
* | Removed duplicate requiring minitest/mock as it is already required in ↵Ronak Jangir2015-08-261-1/+0
| | | | | | | | method_call_assertions
* | Cleaned up generators tests using internal assertion helperRonak Jangir2015-08-202-26/+13
| |
* | Updated tests for the generated version number changeDaniel Morris2015-08-161-3/+3
| |
* | make generated scaffold functional tests work inside API enginesyuuji.yaginuma2015-08-091-0/+28
| | | | | | | | | | * set engine's route in setup * use fixture with engine namespace
* | Merge pull request #21043 from ↵Rafael Mendonça França2015-08-061-0/+1
|\ \ | | | | | | | | | | | | y-yagi/loading_fixtures_in_engine_integration_tests set the correct path to `ActionDispatch::IntegrationTest.fixture_path`
| * | set the correct path to `ActionDispatch::IntegrationTest.fixture_path`yuuji.yaginuma2015-07-281-0/+1
| | | | | | | | | | | | | | | `ActionDispatch::IntegrationTest.fixture_path` set by `test_help.rb`, but if the engine, path under the dummy is will be set, fixtures under test was not loaded.
* | | Enable the `api_only` option for API plugins' generatorsRobin Dupret2015-07-231-0/+26
| | | | | | | | | | | | | | | | | | | | | This way, running a generator inside the plugin's directory, files that are not relevant won't be generated (e.g. views or assets). This won't interfere with the application's generators configuration.
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-07 03:24:03 +0000