aboutsummaryrefslogtreecommitdiffstats
path: root/actionpack/lib/action_dispatch/testing/integration.rb
Commit message (Collapse)AuthorAgeFilesLines
...
* Merge pull request #15061 from tgxworld/remove_unnecessary_includeMatthew Draper2014-05-291-6/+0
|\ | | | | Remove unnecessary include for integration tests.
| * Remove unnecessary include for integration tests.Guo Xiang Tan2014-05-111-6/+0
| |
* | Remove unnecessary require of Minitest.Guo Xiang Tan2014-05-241-1/+0
| | | | | | | | Minitest has already been required when calling Minitest.autorun.
* | Form full URI as string to be parsed in Rack::Test.Guo Xiang Tan2014-05-211-7/+5
|/ | | | There are performance gains to be made by avoiding URI setter methods.
* Merge branch 'master' of github.com:lifo/docrailsVijay Dev2013-12-201-1/+1
|\
| * Typos. return -> returns. [ci skip]Lauro Caetano2013-12-031-1/+1
| |
* | Change all `MiniTest` to `Minitest` since, `MiniTest` namespace has been ↵Vipul A M2013-12-181-1/+1
|/ | | | | | renamed to `Minitest` Ref: https://github.com/seattlerb/minitest/blob/master/History.txt
* remove useless `env.merge!(env)` from ActionDispatch::IntegrationTest`Yves Senn2013-07-041-2/+0
|
* Remove deprecated Rails application fallback for integration testingCarlos Antonio da Silva2013-07-021-4/+0
| | | | Set ActionDispatch.test_app instead.
* Require only minitest.Rafael Mendonça França2013-05-221-1/+1
| | | | | minitest/autorun required minitest/spec and we are avoiding to require it.
* Eliminate minitest warningsSam Ruby2013-05-171-1/+1
| | | | https://github.com/seattlerb/minitest/commit/9a57c520ceac76abfe6105866f8548a94eb357b6#L15R8
* Revert "Integration tests support the OPTIONS http method"Rafael Mendonça França2013-05-161-7/+1
| | | | | | | | | | | | | | This reverts commit ad46884af567d6f8d6d8d777f372c39e81a560ba. Conflicts: actionpack/CHANGELOG.md actionpack/lib/action_dispatch/testing/integration.rb actionpack/test/controller/integration_test.rb Reason: It will conflict with a lot of test cases. Better to call `process` directly since this is a very uncommon HTTP method. Fixes #10638.
* `Http::Headers` directly modifies the passed environment.Yves Senn2013-03-151-2/+3
| | | | | | | | | The env hash passed to `Http::Headers#new` must be in env format. Also be aware that the passed hash is modified directly. docs and test-cases for setting headers/env in functional tests. Follow up to #9700.
* allow headers and env to be passed in `IntegrationTest`.Yves Senn2013-03-131-34/+34
| | | | Closes #6513.
* Ensure port is set when passed via the process methodAndrew White2013-01-151-1/+1
|
* Inherit from MiniTest::Unit::TestCase instead of MiniTest::SpecRafael Mendonça França2012-12-311-3/+0
|
* Merge branch 'master' of github.com:lifo/docrailsVijay Dev2012-11-031-6/+6
|\ | | | | | | | | | | | | Conflicts: actionpack/lib/action_controller/metal/mime_responds.rb activerecord/lib/active_record/attribute_methods.rb guides/source/working_with_javascript_in_rails.md
| * 1.9 hash syntax changes to docsAvnerCohen2012-10-311-6/+6
| |
* | Make caller attribute in deprecation methods optionalAlexey Gaziev2012-10-301-2/+1
| |
* | Add missing require for minitest assertions. Breaks calling 'app' in console ↵Jeremy Kemper2012-10-251-0/+1
|/ | | | otherwise. See 94248ffe1e6f815b8ffab4eb752b60c1e4459d25.
* Register AD::IntegrationTest for minitest's spec DSLMike Moore2012-09-241-0/+3
|
* Merge pull request #7530 from robin850/masterXavier Noria2012-09-051-1/+1
|\ | | | | Fix a typo in AD
| * Fix a typoRobin Dupret2012-09-051-1/+1
| |
* | removes usage of Object#in? from the code base (the method remains defined ↵Xavier Noria2012-08-061-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | by Active Support) Selecting which key extensions to include in active_support/rails made apparent the systematic usage of Object#in? in the code base. After some discussion in https://github.com/rails/rails/commit/5ea6b0df9a36d033f21b52049426257a4637028d we decided to remove it and use plain Ruby, which seems enough for this particular idiom. In this commit the refactor has been made case by case. Sometimes include? is the natural alternative, others a simple || is the way you actually spell the condition in your head, others a case statement seems more appropriate. I have chosen the one I liked the most in each case.
* | load active_support/core_ext/object/inclusion in active_support/railsXavier Noria2012-08-021-1/+0
|/
* Include routes.mounted_helpers into integration testsPiotr Sarnacki2012-06-011-2/+5
| | | | | | | | | | | | | | | In integration tests, you might want to use helpers from engines that you mounted in your application. It's not hard to add it by yourself, but it's unneeded boilerplate. mounted_helpers are now included by default. That means that given engine mounted like: mount Foo::Engine => "/foo", :as => "foo" you will be able to use paths from this engine in tests this way: foo.root_path #=> "/foo" (closes #6573)
* references to the old behavior removedMikhail Vaysman2012-05-251-4/+3
|
* Refactor the handling of default_url_options in integration testsAndrew White2012-05-101-7/+24
| | | | | | | | | | | | This commit improves the handling of default_url_options in integration tests by making behave closer to how a real application operates. Specifically the following issues have been addressed: * Options specified in routes.rb are used (fixes #546) * Options specified in controllers are used * Request parameters are recalled correctly * Tests can override default_url_options directly
* consistently mention first patch, then putXavier Noria2012-02-241-1/+1
| | | | | | There was a mix, sometimes patch first, sometimes put first. Use always patch first, since this is going to be the primary verb for updates.
* Add config.default_method_for_update to support PATCHDavid Lee2012-02-221-7/+19
| | | | | | | | | | | | | | | | PATCH is the correct HTML verb to map to the #update action. The semantics for PATCH allows for partial updates, whereas PUT requires a complete replacement. Changes: * adds config.default_method_for_update you can set to :patch * optionally use PATCH instead of PUT in resource routes and forms * adds the #patch verb to routes to detect PATCH requests * adds #patch? to Request * changes documentation and comments to indicate support for PATCH This change maintains complete backwards compatibility by keeping :put as the default for config.default_method_for_update.
* Integration tests support the OPTIONS http methodJeremy Kemper2012-02-191-1/+7
|
* Use MiniTest::Assertions instead of Test::Unit::AssertionsRafael Mendonça França2012-01-061-2/+1
|
* remove Rails application fallback from AD::IntegrationTestSergey Nartimov2011-12-231-3/+6
| | | | set AD::IntegrationTest.app in railtie initializer
* Revert "Make process reuse the env var passed as argument"Santiago Pastorino2011-09-241-4/+4
| | | | This reverts commit 0e4748cd415660eb91e63d50aa15cdd027c612dd.
* remove warning: assigned but unused variableSantiago Pastorino2011-06-081-3/+0
|
* Remove extra white spaces on ActionPack docs.Sebastian Martinez2011-05-231-1/+1
|
* Remove `#among?` from Active SupportPrem Sichanugrist2011-04-131-1/+1
| | | | | | After a long list of discussion about the performance problem from using varargs and the reason that we can't find a great pair for it, it would be best to remove support for it for now. It will come back if we can find a good pair for it. For now, Bon Voyage, `#among?`.
* Change Object#either? to Object#among? -- thanks to @jamesarosen for the ↵David Heinemeier Hansson2011-04-121-1/+1
| | | | suggestion!
* Using Object#in? and Object#either? in various placesPrem Sichanugrist2011-04-111-1/+2
| | | | There're a lot of places in Rails source code which make a lot of sense to switching to Object#in? or Object#either? instead of using [].include?.
* Make process reuse the env var passed as argumentSantiago Pastorino2011-04-061-5/+4
|
* Fix grammar, formatting, and cross referencesJohn Firebaugh2011-03-281-8/+8
|
* just use aliasAaron Patterson2010-11-301-3/+1
|
* Remove bazillion warnings from AP suite.José Valim2010-11-231-1/+1
|
* add respond_to? to ActionDispatch::Integration::RunnerSven Fuchs2010-11-221-0/+4
| | | | since Runner uses method_missing to delegate to the integration session it also should define respond_to? accordingly
* Fix an error on 1.8.7.José Valim2010-09-291-1/+1
|
* Avoid (@_var ||= nil) pattern by using initialize methods and ensuring ↵José Valim2010-09-291-0/+1
| | | | everyone calls super as expected.
* Initialize @app if it doesn't exists.Emilio Tagua2010-09-281-1/+1
|
* Avoid uninitialized variable warning, reuse @integration_session.Emilio Tagua2010-09-271-8/+14
|
* Fix the precedence issue hereSantiago Pastorino2010-09-261-1/+1
|
* Not need to do this double ternarySantiago Pastorino2010-09-261-1/+1
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-01 05:52:00 +0000