aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source/testing.md
Commit message (Collapse)AuthorAgeFilesLines
...
* 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
|
* Remove duplicate description of the previous line [ci skip]Zachary Scott2014-12-221-1/+1
|
* Fix NOTE for method naming in Ruby and add intro sentence to next section.Zachary Scott2014-12-221-1/+3
| | | | [ci skip]
* Removed run-on sentence and replace with sectional comments [ci skip]Zachary Scott2014-12-221-2/+2
|
* Better explain how test() methods get defined and kill this run-on sentence.Zachary Scott2014-12-221-2/+2
| | | | [ci skip]
* We may only look at some of the methods available from TestCase [ci skip]Zachary Scott2014-12-221-1/+1
|
* Better explain what `test_helper.rb` is designed for [ci skip]Zachary Scott2014-12-221-1/+1
|
* Testing guide grammar fixJon Atack2014-12-211-1/+1
| | | [skip ci]
* We will be using the application already created in the Getting Started guide.Zachary Scott2014-12-201-4/+2
| | | | [ci skip]
* Follow-up to d9710212 [skip ci]Jon Atack2014-12-211-1/+1
|
* Fixture data is accessible by a local method, and not a variable [ci skip]Zachary Scott2014-12-201-2/+2
|
* Shorten the explaination of this to fit on one line [ci skip]Zachary Scott2014-12-201-1/+1
|
* s/folder/directory [ci skip]Zachary Scott2014-12-201-7/+7
|
* "In PostgreSQL, just superusers.." => "In PostgreSQL, only superusers.."Zachary Scott2014-12-201-1/+1
| | | | [ci skip]
* Make sure this section is rendered as a `NOTE` and remove redundant sentence.Zachary Scott2014-12-201-5/+1
| | | | [ci skip]
* Add note about the association between the two fixture files and how they're ↵Zachary Scott2014-12-201-0/+2
| | | | | | connection. [ci skip]
* Remove YAML implementation detail, as we're not trying to document all ofZachary Scott2014-12-201-1/+1
| | | | YAML's behavior in this guide. [ci skip]
* Remove use of "very" [ci skip]Zachary Scott2014-12-201-1/+1
|
* Describe the mailer and helpers directories which are generated by `rails new`.Zachary Scott2014-12-201-1/+1
| | | | [ci skip]
* Update comment regarding test environment with help from @matthewd [ci skip]Zachary Scott2014-12-201-1/+3
|
* Adding a tip in the guides about possible database permission problems onandrey.nering@gmail.com2014-12-091-0/+2
| | | | | | loading fixtures to the database. Reference #17542
* [Testing guide] Using "Fixtures API" consistentlyPrathamesh Sonpatki2014-11-301-1/+1
| | | | | | | | | - In guides, "API" is used consistently instead of "api". - Reason behind replacing "fixtures API" to "Fixtures API" is because here we are referring to the concept of "fixtures". In other places in the guide "fixture" OR "fixtures" is referred to the single or multiple instances of test data. - This is also followup of https://github.com/rails/docrails/commit/aa9d1332b20305dd860b21a7ada06c5252bebad5#commitcomment-8497376.
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-14 16:02:37 +0000