aboutsummaryrefslogtreecommitdiffstats
path: root/railties/test/application/initializers/frameworks_test.rb
Commit message (Collapse)AuthorAgeFilesLines
* Replace `assert !` with `assert_not`Daniel Colson2018-04-191-1/+1
| | | | | This autocorrects the violations after adding a custom cop in 3305c78dcd.
* Use assert_predicate and assert_not_predicateDaniel Colson2018-01-251-1/+1
|
* Run in-app rails commands via fork+load where possibleMatthew Draper2017-09-041-8/+4
| | | | | While this avoids shell argument parsing, we still pass through everything in our stack.
* Preload Rails component gems in railties testsMatthew Draper2017-09-041-1/+1
|
* Adding frozen_string_literal pragma to Railties.Pat Allan2017-08-141-0/+2
|
* Revert "Merge pull request #29540 from kirs/rubocop-frozen-string"Matthew Draper2017-07-021-1/+0
| | | | | This reverts commit 3420a14590c0e6915d8b6c242887f74adb4120f9, reversing changes made to afb66a5a598ce4ac74ad84b125a5abf046dcf5aa.
* Enforce frozen string in RubocopKir Shatrov2017-07-011-0/+1
|
* Clear active connections after initializationEugene Kenny2017-02-171-0/+8
| | | | | | | | | | | | | Any connections that were checked out during initialization should be checked back in before the first request is processed, for two reasons: - Returning the connection to the pool allows it to be health checked before it's used again. If the connection dies before the first request arrives, the health check will replace it with a new one. - If the thread that initialized Rails is not the same thread that will be performing work, checking in the connection will allow it to be reused instead of being stuck to the initialization thread forever.
* `#tables` and `#table_exists?` and returns only tables and not viewsRafael Mendonça França2016-12-291-5/+3
|
* Add more rubocop rules about whitespacesRafael Mendonça França2016-10-291-1/+1
|
* applies new string literal convention in railties/testXavier Noria2016-08-061-7/+7
| | | | | The current code base is not uniform. After some discussion, we have chosen to go with double quotes by default.
* Remove unused boot_rails method and it's usagePrathamesh Sonpatki2016-07-041-1/+0
| | | | | - The `boot_rails` method from abstract_unit.rb is empty after 2abcdfd978fdcd491576a237e8c6b. - So let's remove it and its usage.
* remove args from assert_nothing_raised in testsTara Scherner de la Fuente2016-02-221-1/+1
|
* Be consistent in testing outputs from railties test and use /bin/rails ↵Vipul A M2016-01-241-2/+2
| | | | | | everywhere(the default behaviour now) instead of mix of /bin/rake /bin/rails everywhere [Ryo Hashimoto & Vipul A M]
* Merge pull request #17388 from akampjes/masterArthur Nogueira Neves2015-10-121-0/+11
|\ | | | | ActionMailer https on URL with force_ssl = true
| * ActionMailer https on URL with force_ssl = trueAndrew Kampjes2015-08-141-0/+11
| | | | | | | | | | | | | | | | | | | | `config.force_ssl = true` will set config.action_mailer.default_url_options = { protocol: 'https' } If you have turned on force_ssl, and then gone to the effort of setting config.action_mailer.default_url_options = {host: 'example.com'} then you are probably pointing people back to your current app and want https on that too.
* | remove unused require ‘set’NehaGautam2015-08-251-1/+0
|/
* tests, railties tests should use `bin/` executables when possible.Yves Senn2015-06-301-2/+2
| | | | | We recommend using the `bin/` executables in our docs and guides. Let's make sure that our tests execute the same code path.
* Use new hash syntaxSantiago Pastorino2015-06-111-1/+1
|
* Add AC::API + its middleware stack integration testSantiago Pastorino2015-06-111-0/+29
|
* Remove deprecate `*_path` helpers in email viewsRafael Mendonça França2015-01-041-1/+0
|
* Expectations firstAkira Matsuda2014-08-281-2/+2
|
* Deprecate `*_path` methods in mailers@schneems and @sgrif2014-07-301-2/+2
| | | | | | | | | | | Email does not support relative links since there is no implicit host. Therefore all links inside of emails must be fully qualified URLs. All path helpers are now deprecated. When removed, the error will give early indication to developers to use `*_url` methods instead. Currently if a developer uses a `*_path` helper, their tests and `mail_view` will not catch the mistake. The only way to see the error is by sending emails in production. Preventing sending out emails with non-working path's is the desired end goal of this PR. Currently path helpers are mixed-in to controllers (the ActionMailer::Base acts as a controller). All `*_url` and `*_path` helpers are made available through the same module. This PR separates this behavior into two modules so we can extend the `*_path` methods to add a Deprecation to them. Once deprecated we can use this same area to raise a NoMethodError and add an informative message directing the developer to use `*_url` instead. The module with warnings is only mixed in when a controller returns false from the newly added `supports_relative_path?`. Paired @sgrif & @schneems
* Revise 'sqlite3:' URL handling for smoother upgradesMatthew Draper2014-04-031-2/+2
| | | | | | | | | | | | | | | | Restore the 4.0 behaviour for 'sqlite3:///', but deprecate it. We'll change to the absolute-path interpretation in 4.2. The current "correct" spellings for in-memory, relative, and absolute URLs, respectively, are: sqlite3::memory: sqlite3:relative/path sqlite3:/full/path Substantially reverses/defers fbb79b517f3127ba620fedd01849f9628b78d6ce. Uncovered by @guilleiguaran while investigating #14495, though that sounds like a different issue.
* Use Full path to sqlite database in testsschneems2013-12-221-1/+1
|
* build fix: railties tests used deprecated `SchemaCache` methods.Yves Senn2013-07-041-2/+2
|
* Calls to the application constant have been refactored to usewangjohn2013-06-101-3/+3
| | | | | Rails.application when drawing routes and creating other configurations on the application.
* Move background jobs to the 'jobs' branch until fully baked. Not shipping ↵Jeremy Kemper2012-12-211-16/+0
| | | | with Rails 4.0.
* Removing warning : ambiguous first argumentArun Agrawal2012-11-111-2/+2
|
* Remove the queue container. Premature consolidation. Set up and maintain ↵Jeremy Kemper2012-10-121-3/+2
| | | | queues in the classes that use them instead.
* Use String#exclude? to make sure that Active Support is not loaded whenRafael Mendonça França2012-10-041-1/+1
| | | | | | | bare is true. We need to change this since coffee-rails loads ActionView that loads core_ext/array/access.
* Move queue classes to ActiveSupportSantiago Pastorino2012-09-141-3/+3
|
* Allow users to configure the queue for the mailersRafael Mendonça França2012-09-121-0/+17
| | | | | | | | | | | | This allow the users to do: config.action_mailer.queue = MyQueue.new and class UsersMailer < ActionMailer::Base self.queue = MyQueue.new end
* fixed support for DATABASE_URL for rake db tasksGrace Liu2012-09-111-0/+32
| | | | | | | | | | | | - added tests to confirm establish_connection uses DATABASE_URL and Rails.env correctly even when no arguments are passed in. - updated rake db tasks to support DATABASE_URL, and added tests to confirm correct behavior for these rake tasks. (Removed establish_connection call from some tasks since in those cases the :environment task already made sure the function would be called) - updated Resolver so that when it resolves the database url, it removes hash values with empty strings from the config spec (e.g. to support connection to postgresql when no username is specified).
* Extract ActiveRecord::SessionStore from RailsPrem Sichanugrist2012-08-241-20/+0
| | | | | This functionality will be available from gem `active_record-session_store` instead.
* Remove default match without specified methodJose and Yehuda2012-04-241-1/+1
| | | | | | | | | | | | | | | | In the current router DSL, using the +match+ DSL method will match all verbs for the path to the specified endpoint. In the vast majority of cases, people are currently using +match+ when they actually mean +get+. This introduces security implications. This commit disallows calling +match+ without an HTTP verb constraint by default. To explicitly match all verbs, this commit also adds a :via => :all option to +match+. Closes #5964
* Remove --http.José Valim2012-03-141-27/+0
|
* Add ActionController::HTTPSantiago Pastorino2012-03-141-0/+27
| | | | | | More info http://edgeguides.rubyonrails.org/api_app.html [Carlos Antonio da Silva & Santiago Pastorino]
* Fix broken testsSantiago Pastorino2012-03-101-1/+2
|
* Use one system call whenever possible, group rake and Dir.chdir callsCarlos Antonio da Silva2012-03-081-9/+4
|
* Support judgement expired schema cache dump.kennyj2012-03-011-0/+14
|
* Load db/schema_cache.dump duaring boot time.kennyj2012-03-011-0/+12
|
* convert railties to use AS::TestCaseAaron Patterson2012-01-051-1/+1
|
* remove checks for encodings availabilitySergey Nartimov2011-12-251-1/+1
|
* Fix testcase an error on ruby 1.8.x.kennyj2011-12-091-2/+3
| | | | | | In Ruby 1.8.x, config.encoding sets $KCODE. Therefore, the possible values are UTF8, SJIS, or EUC. And, if we set SJIS, we'll has the error. Because some rails sources are written in utf-8 encoding.
* Assign config.encoding to AD::Response.default_charset at the initialization ↵kennyj2011-12-071-0/+6
| | | | time.
* Solve the RAILS_ENV problem in the railties tests in a more generic wayJon Leighton2011-06-061-3/+1
|
* framework_test.rb also dependent on RAILS_ENV=developmentArun Agrawal2011-06-061-0/+6
|
* Fix tests to reflect IdentityMap no longer defaultDavid Lee2011-05-101-1/+1
| | | | Broke in 0e1dcae1857db4f6721561caff38d8be748d0b40
* Fix typo.Emilio Tagua2010-11-191-1/+1
|