aboutsummaryrefslogtreecommitdiffstats
path: root/actionpack/lib/action_dispatch/testing
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'master' of github.com:lifo/docrailsVijay Dev2012-11-036-46/+46
|\ | | | | | | | | | | | | 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-316-46/+46
| |
* | 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
| |
* | Move action_controller/vendor/html-scanner to action_viewPiotr Sarnacki2012-08-283-3/+4
| | | | | | | | | | | | This is another step in moving Action View's dependencies in Action Pack to Action View itself. Also, HtmlScanner seems to be better suited for views rather than controllers.
* | 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-023-3/+0
| |
* | load active_support/core_ext/object/blank in active_support/railsXavier Noria2012-08-021-1/+0
| |
* | Updated with_routing example to 3.x syntax [ci skip]Wojciech Wnętrzak2012-07-131-7/+4
|/
* make the default environment have actual defaultsAaron Patterson2012-07-031-1/+7
| | | | | | instead of deleting keys on every instantiation, create defaults we actually use. eventually we can pass an environment in to the request, and create a new req / res object on each call.
* 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
|
* Fix bug when Rails.application is defined but is nil. See #881Marc-Andre Lafortune2012-05-211-1/+1
|
* Correct order of expected and actual argumentsAndrew White2012-05-201-1/+1
|
* Raise Assertion instead of RoutingError for routing assertion failures.David Chelimsky2012-05-201-7/+13
| | | | | | | | | | | | | Before this change, assert_recognizes, assert_generates, and assert_routing raised ActionController::RoutingError when they failed to recognize the route. This commit changes them to raise Assertion instead. This aligns with convention for logical failures, and supports reporting tools that care about the difference between logical failures and errors e.g. the summary at the end of a test run. - Fixes #5899
* Removing ==Examples and last blank lines of docs from actionpackFrancesco Rodriguez2012-05-155-24/+0
|
* 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
* Allows assert_redirected_to to accept a regular expressionAndy Lindeman2012-05-031-13/+20
|
* Merge pull request #5716 from jurriaan/tr-gsub-cleanupSantiago Pastorino2012-04-041-1/+1
|\ | | | | Updated/changed unneeded tr/gsubs
| * Updated/changed useless tr/gsubsJurriaan Pruis2012-04-031-1/+1
| |
* | No need to extend ActiveSupport::Extend hereOscar Del Ben2012-04-041-2/+0
|/
* Merge branch 'master' of github.com:lifo/docrailsVijay Dev2012-04-011-1/+1
|\
| * :success includes the whole 200 range, not just 200.Erich Menge2012-04-011-1/+1
| | | | | | | | | | # File lib/rack/response.rb, line 114 114: def successful?; @status >= 200 && @status < 300; end
* | Remove not needed requiresSantiago Pastorino2012-03-311-1/+0
| |
* | Remove the leading \n added by textarea on assert_selectSantiago Pastorino2012-03-301-0/+1
|/
* strip null bytes from Location header as wellBrian Lopez2012-03-151-1/+1
| | | | add tests for stripping \r\n chars since that's already happening
* Merge pull request #5219 from ↵Aaron Patterson2012-02-291-4/+3
|\ | | | | | | | | mattfawcett/2781-fix-querystring-route-constraint-for-testing Fix for #2781
| * Fix the assert_recognizes test method so that it works when there areMatt Fawcett2012-02-241-4/+3
| | | | | | | | constraints on the querystring. Issue #2781
* | 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.
* Merge pull request #5082 from ↵Aaron Patterson2012-02-201-1/+2
|\ | | | | | | | | willbryant/assigns_should_not_stringify_values_master assigns(:foo) should not convert @foo's keys to strings if it happens to be a hash
| * assigns(:foo) should not convert @foo's keys to strings if it happens to be ↵Will Bryant2012-02-181-1/+2
| | | | | | | | a hash
* | Integration tests support the OPTIONS http methodJeremy Kemper2012-02-191-1/+7
|/
* Stop referring to Atom as "ATOM"Tom Stuart2012-02-051-1/+1
| | | | | | $ curl -s http://www.ietf.org/rfc/rfc4287 | grep -io ATOM | sort | uniq -c 582 atom 175 Atom
* Remove assert_select_feed from assert_select_encoded documentationTom Stuart2012-02-051-2/+2
| | | | | | This documentation came from the assert_select plugin, but the assert_select_feed method was omitted when the plugin was merged into Rails in 3142502964f94d6144312ae2c368b4c4589fa25a.
* Replaced all 'for' loops with Enumerable#eachNathan Broadbent2012-01-301-2/+2
|
* Use MiniTest::Assertions instead of Test::Unit::AssertionsRafael Mendonça França2012-01-061-2/+1
|
* use assert_equal and assert_operatorAaron Patterson2012-01-061-5/+8
|
* use sprintf rather than build_messageAaron Patterson2012-01-061-4/+6
|
* Just use assert_equalAaron Patterson2012-01-061-3/+2
|
* refactor assert_responseAaron Patterson2012-01-061-7/+10
|
* test response assertionsAaron Patterson2012-01-061-8/+0
|
* no need for assert_blockAaron Patterson2012-01-061-3/+3
|
* stop using build_message for creating a stringAaron Patterson2012-01-061-1/+1
|
* just use assert and refute rather than building messagesAaron Patterson2012-01-061-6/+2
|
* remove Rails application fallback from AD::IntegrationTestSergey Nartimov2011-12-231-3/+6
| | | | set AD::IntegrationTest.app in railtie initializer
* TestCase should respect the view_assigns API instead of pulling variables on ↵José Valim2011-10-021-6/+1
| | | | its own.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-20 18:14:04 +0000