aboutsummaryrefslogtreecommitdiffstats
path: root/railties/test/application
Commit message (Collapse)AuthorAgeFilesLines
* s/and and run/and runs/David Chapman2013-03-261-1/+1
| | | | Fixing some typos/grammar.
* Fixed typo in railties/testPrathamesh Sonpatki2013-03-252-2/+2
|
* Controller name pluralizedPrathamesh Sonpatki2013-03-251-2/+2
|
* Fix some typosVipul A M2013-03-243-3/+3
|
* Don't kill the consoleJon Leighton2013-03-221-10/+2
| | | | | Use the "quit" command instead. This seems to prevents some weirdness on OS X. See #9761.
* Send SIGTERM, not SIGQUIT.Jon Leighton2013-03-221-1/+1
| | | | | | SIGTERM is the correct signal for a graceful exit. This will hopefully resolve #9761.
* Revert "make new rails apps log to STDOUT"Steve Klabnik2013-03-151-21/+0
| | | | | | This reverts commit b7d9d6e2cd5082d269dafbc0316e2107febe1451. Per discussion with @jeremy and @rubys on Campfire.
* make new rails apps log to STDOUTTerence Lee2013-03-151-0/+21
|
* Replace assert_(no_)match args from regexps to strings to remove warningsCarlos Antonio da Silva2013-03-111-40/+40
| | | | | | Using regexps as arguments without parentheses end up raising: warning: ambiguous first argument; put parentheses or even spaces
* Make sure that the test case is run under test envPrem Sichanugrist2013-03-111-1/+17
| | | | | | * Unset $RAILS_ENV that got set by abstract_unit to trigger the default. * split out environment setting since Ruby 1.9.3 doesn't support inline ENV setting.
* Fix test failure introduced in 3ed41e57Prem Sichanugrist2013-03-111-5/+3
| | | | I forgot to run the test suit after changing the task name. :bomb:
* Make sure that `rails test` load test in test envPrem Sichanugrist2013-03-091-1/+44
|
* Update Rake tasks to call `rails test` insteadPrem Sichanugrist2013-03-091-10/+13
| | | | | Also, print out deprecation warning for other rake tasks except `rake test` and `rake` (default)
* Improve wording for rails test commandDalibor Nasevic2013-03-091-8/+8
|
* Load fixtures only when running suites, or `-f`Prem Sichanugrist2013-03-091-0/+51
| | | | | | * `rails test -f` will run the test suites with all fixtures loaded * New application will now generated without `fixtures :all` line enabled by default.
* Add support for MiniTest flags in TestRunnerPrem Sichanugrist2013-03-091-0/+21
| | | | | Any flags that got set will be passed through to MiniTest::Unit.runner, such as `-n`, `-s-, and `-v`.
* Add `rails test` command to run the test suitePrem Sichanugrist and Chris Toomey2013-03-091-0/+183
| | | | | | | | | | | | | | | | | | | To run the whole test suite: $ rails test To run the test file(s): $ rails test test/unit/foo_test.rb [test/unit/bar_test.rb ...] To run the test suite $ rails test [models,helpers,units,controllers,mailers,...] For more information, see `rails test --help`. This command will eventually replacing `rake test:*`, and `rake test` command will actually invoking `rails test` instead.
* Fix race condition in testJon Leighton2013-03-091-2/+2
| | | | | | | | | | | This should fix travis. For real this time! This is the one! The readpartial(100) meant that an earlier assert_stdout could chomp up the output that a later assert_stdout wants, meaning that the later assertion fails. Reading only 1 byte at a time ensure that we don't read any more than is necessary to verify the assertion.
* Bump up timeoutsJon Leighton2013-03-091-3/+3
| | | | | | This should fix travis. Also ensuring that we don't try to kill when pid is nil.
* The console --sandbox transaction should not be joinableJon Leighton2013-03-081-10/+8
| | | | Thanks @neerajdotname for noticing this bug.
* Fix rails console --sandboxJon Leighton2013-03-081-8/+74
| | | | | | I've also added a proper acceptance test which reproduced the issue. Closes #9513, #9515.
* Bring config.allow_concurrency backJosé Valim2013-03-031-0/+6
| | | | | Since the Rack::Lock still exists in development, let's provide a way to disable it explicitly.
* Remove hard coded references to Active Record in railtiesJosé Valim2013-03-021-13/+0
|
* remove uncommented railties boot_test.rbYves Senn2013-02-211-20/+0
|
* run the load_structure test in the test environmentTerence Lee2013-02-211-3/+10
|
* test DATABASE_URL without database.yml aroundTerence Lee2013-02-211-0/+2
|
* Fix rake routes output in railties testCarlos Antonio da Silva2013-02-191-2/+4
|
* Revert "Deprecate the `eager_load_paths` configuration"Andrew White2013-02-192-6/+6
| | | | | | | | | | | Because of the possibility of lib being unintentionally eager loaded it's been agreed that we'll leave autoload paths and eager load paths separate for Rails 4.0. This reverts commit 0757b3388ffe4f44b60de950d40e18ef05055931. Conflicts: railties/CHANGELOG.md
* editorial tweaksXavier Noria2013-02-191-1/+1
|
* Use strip_heredoc in the tests as well.Steve Klabnik2013-02-181-5/+6
| | | | Thanks @sikachu. :sweat_smile:
* Add message when you have no routes defined.Steve Klabnik2013-02-181-0/+15
| | | | | | Print a message in both `rake routes` and at GET "/rails/info/routes" that lets you know you have no routes defined, as well as linking to the Rails Guide on the topic.
* Remove BestStandardsSupport middlewareGuillermo Iguaran2013-01-292-32/+1
|
* Deprecate the `eager_load_paths` configurationAndrew White2013-01-242-6/+6
| | | | | | | | | | Since the default in Rails 4.0 is to run in 'threadsafe' mode we need to eager load all of the paths in `autoload_paths` so we alias `eager_load_paths` to it. This may have unintended consequences if you have added 'lib' to `autoload_paths` such as loading unneeded code or code intended only for development and/or test environments. If this applies to your application you should thoroughly check what is being eager loaded.
* Revert "Set the default timezone after the initialization since the ↵Carlos Antonio da Silva2013-01-221-11/+1
| | | | | | configuration" This reverts commit 39374aa925a7d670b039c0c0c9aa9f4aef19466b.
* Restore and adapt the implementation reverted atRafael Mendonça França2013-01-191-0/+48
| | | | | | https://github.com/rails/rails/commit/cc1c3c5be061e7572018f734e5239750ab449e3f Now instead of raise, we log by default in development and test
* script => binAkira Matsuda2013-01-181-6/+6
|
* allow :dirs option for .enumerateBrian D. Burns2013-01-151-0/+39
| | | | | | Allows custom rake tasks to be defined using: SourceAnnotationExtractor.enumerate 'TODO|FIXME', dirs: %w(app lib), tag: true
* Account for ignored cookie set by turbolinksNick Reed2013-01-141-6/+6
|
* Add regression test to #8907Rafael Mendonça França2013-01-141-0/+31
|
* remove performance tests from the default stackYves Senn2013-01-101-25/+0
|
* Revert "unpermitted params" exception -- it's just not going to work. See ↵David Heinemeier Hansson2013-01-081-48/+0
| | | | the discussion on https://github.com/rails/strong_parameters/pull/75.
* Introduce ./bin for your app's executables: bin/bundle, bin/rails, bin/rake. ↵Jeremy Kemper2013-01-062-7/+3
| | | | Executable scripts are versioned code like the rest of your app. To generate a stub for a bundled gem: 'bundle binstubs unicorn' and 'git add bin/unicorn'
* Move config.filter_parameters to you own initializer fileRafael Mendonça França2013-01-051-2/+2
| | | | This is very rarely changed and does not deserve to be in application.rb
* Assert config.filter_parameters should be able to be set in a initializerRafael Mendonça França2013-01-051-0/+10
|
* Remove warning "ambiguous first argument"Carlos Antonio da Silva2013-01-051-1/+1
|
* Rename the configuration to raise_on_unpermitted_parametersRafael Mendonça França2013-01-051-9/+9
| | | | Also changed the exception to UnpermittedParameters
* Ensure that raise_on_unexpected_params configuration will workRafael Mendonça França2013-01-051-0/+48
|
* Set the default timezone after the initialization since the configurationRafael Mendonça França2013-01-041-1/+11
| | | | | | now lives in the application initializers. Fix #8711
* Restore original remote_ip algorithm.Andre Arko2013-01-021-1/+1
| | | | | | | | | | | Proxy servers add X-Forwarded-For headers, resulting in a list of IPs. We remove trusted IP values, and then take the last given value, assuming that it is the most likely to be the correct, unfaked value. See [1] for a very thorough discussion of why that is the best option we have at the moment. [1]: http://blog.gingerlime.com/2012/rails-ip-spoofing-vulnerabilities-and-protection/ Fixes #7979
* Fix usage of lambda as a Rack endpointJiri Pospisil2012-12-311-1/+1
| | | | The response body needs to respond_to? :each.
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-03 07:47:12 +0000