aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source/testing.md
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #19322 from ↵Rafael Mendonça França2015-03-131-1/+1
|\ | | | | | | | | AndrewHendrie/AndrewHendrie-guides-testing-partials-patch Asserting partials modification
| * Asserting partials modificationAndrew Hendrie2015-03-131-1/+1
| | | | | | Changed "create Articles view" to "new article view". The create action doesn't typically have a view assigned to it. The view that's being referred to is the 'new' Article view.
* | Fix typo in the “Testing Your Mailers” docsMarius Butuc2015-03-121-1/+1
|/ | | * [ci skip]
* Changed 'blank space' to 'blank line'Andrew Hendrie2015-03-091-1/+1
| | | Line 85 stated that fixtures are typically separated by a blank space. I changed the wording to blank line because blank space could be misinterpreted as a non-breaking space character when in reality, each fixture record (in YAML) is separated by a blank line.
* add `ActiveJob::TestCase` to list of classes providing for test [ci skip]yuuji.yaginuma2015-02-281-0/+1
|
* Tiny documentation edits [ci skip]Robin Dupret2015-02-151-1/+2
|
* guides, various testing guide changes. [ci skip]Yves Senn2015-02-111-7/+15
| | | | /cc @zzak
* Migrating xhr methods to keyword arguments syntaxKir Shatrov2015-02-011-2/+2
| | | | | | | | | | | | in `ActionController::TestCase` and `ActionDispatch::Integration` Old syntax: `xhr :get, :create, params: { id: 1 }` New syntax example: `get :create, params: { id: 1 }, xhr: true`
* Consistent usage of spaces in hashes across our codebaseRafael Mendonça França2015-01-291-8/+8
|
* Use fixed fonts only in the name of the parameterRafael Mendonça França2015-01-291-3/+3
|
* Switch to kwargs in ActionController::TestCase and ActionDispatch::IntegrationKir Shatrov2015-01-291-18/+27
| | | | | | | | Non-kwargs requests are deprecated now. Guides are updated as well. `post url, nil, nil, { a: 'b' }` doesn't make sense. `post url, params: { y: x }, session: { a: 'b' }` would be an explicit way to do the same
* Fix test case class in the testing guide [ci skip]Rafael Mendonça França2015-01-211-1/+1
|
* Merge branch 'master' of github.com:rails/docrailsVijay Dev2015-01-151-7/+54
|\
| * Better example of `teardown` method in test guideKir Shatrov2015-01-031-4/+2
| | | | | | rails/rails#18305, thanks for @dhh suggestion
| * Demonstrate example of `assert_emails` in testing guideKir Shatrov2015-01-031-3/+4
| | | | | | rails/rails#18305, thanks for @dhh suggestion
| * Docs for controller test helpersKir Shatrov2015-01-031-0/+35
| | | | | | | | rails/rails#18305
| * Avoid double negation in test guideKir Shatrov2015-01-031-1/+1
| | | | | | | | rails/rails#18305
| * Section about testing xhr requestsKir Shatrov2015-01-031-0/+13
| | | | | | | | rails/rails#18305
* | - Changed `IN` to `ON` in markdown renderer conditionVipul A M2015-01-141-1/+1
|/ | | | - Changed `IN` to `ON` in all note sentences in guides.
* fix rake command typo in Testing guide [ci skip]yuuji.yaginuma2014-12-311-1/+1
|
* Replace exhaustive list of methods with pointer to API docs. [ci skip]Zachary Scott2014-12-301-11/+1
|
* Add result of running articles_routes_test and point to more information forZachary Scott2014-12-301-0/+16
| | | | RoutingAssertions. [ci skip]
* Move request tests after functional and before views, and move helper testsZachary Scott2014-12-301-50/+50
| | | | after views. [ci skip]
* Make "Testing Views" separate section, move "Setup and Teardown" intoZachary Scott2014-12-301-88/+85
| | | | | | functional testing section and implement :show, :destroy, and :update tests. [ci skip]
* Add implement integration test to Testing Guide. [ci skip]Zachary Scott2014-12-301-0/+75
|
* Replace exhaustive list of helper methods with pointers to helper classes foundZachary Scott2014-12-301-16/+7
| | | | in the Action Dispatch Integration module. [ci skip]
* Remove this line which was added by accident [ci skip]Zachary Scott2014-12-301-2/+0
|
* Move Rake tasks list to a smaller heading section earlier in the guide.Zachary Scott2014-12-291-21/+21
| | | | | It makes more sense here, rather than after explaining all of the testing facilities of Rails. [ci skip]
* Condense notes regarding Minitest and its available assertions removed in:Zachary Scott2014-12-291-38/+19
| | | | | | | | 82b75eda70f8c30f7c418e7350532a3a0ed2a8c3 Also explain how Rails inherits capabilities from Minitest. Test classes should be roughly the same based on this information, we can address them at a high level when introducing the first test case. [ci skip]
* Remove redundant information about Minitest, which is already covered whenZachary Scott2014-12-291-8/+0
| | | | assertions are introduced. [ci skip]
* Move longer form example from integration guide to api reference, below anZachary Scott2014-12-291-74/+0
| | | | | | | | existing example. [ci skip] My reasoning is that this is probably too much information for the complete Rails testing guide, as we're trying to cover testing all aspects of the framework.
* Grammar pass through Integration Testing section [ci skip]Zachary Scott2014-12-291-3/+3
|
* Remove pre-4.2 comment about missing `assert_select` [ci skip]Zachary Scott2014-12-291-2/+0
|
* Update link to rails-dom-testing documentation [ci skip]Zachary Scott2014-12-291-1/+1
|
* Pass through `assert_select` testing guide [ci skip]Zachary Scott2014-12-291-4/+9
|
* Implement testing `flash` notices into our blog app [ci skip]Zachary Scott2014-12-291-3/+62
|
* Pass through Testing Templates and Layouts section [ci skip]Zachary Scott2014-12-291-11/+13
|
* These are technically objects [ci skip]Zachary Scott2014-12-291-2/+2
|
* Rephrase Four Hashes of the Apocalypse [ci skip]Zachary Scott2014-12-291-1/+1
|
* Compare http request type with test equivalent methods, and application ↵Zachary Scott2014-12-291-2/+2
| | | | | | use-cases. Briefly explain difference between Functional and Request type tests. [ci skip]
* Rephrase functional testing in its relation to Rails Controller Unit Testing.Zachary Scott2014-12-291-1/+1
| | | | [ci skip]
* Add example to get Errored test to pass in Testing guide [ci skip]Zachary Scott2014-12-251-0/+13
|
* warn about reading guides in GitHubXavier Noria2014-12-231-0/+2
| | | | References #18148.
* Remove this section, it adds no real value [ci skip]Zachary Scott2014-12-221-4/+0
|
* Add subheadings for these sections [ci skip]Zachary Scott2014-12-221-0/+4
|
* I'm sorry but I would rather not link to a 7 year old blog post [ci skip]Zachary Scott2014-12-221-2/+0
|
* Remove this line since we are using Rake to run our tests [ci skip]Zachary Scott2014-12-221-1/+1
|
* s/are edited and rerun/required modifications [ci skip]Zachary Scott2014-12-221-2/+2
|
* document the return of `db:test:prepare`. Closes #18136. [ci skip]Yves Senn2014-12-221-1/+10
| | | | | | This is a doc follow-up to #17739. /cc @zzak
* Better explain number of assertions per test [ci skip]Zachary Scott2014-12-221-1/+1
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-01 15:47:23 +0000