Commit message (Collapse) | Author | Age | Files | Lines | ||
---|---|---|---|---|---|---|
... | ||||||
* | Pass through `assert_select` testing guide [ci skip] | Zachary Scott | 2014-12-29 | 1 | -4/+9 | |
| | ||||||
* | Implement testing `flash` notices into our blog app [ci skip] | Zachary Scott | 2014-12-29 | 1 | -3/+62 | |
| | ||||||
* | Pass through Testing Templates and Layouts section [ci skip] | Zachary Scott | 2014-12-29 | 1 | -11/+13 | |
| | ||||||
* | These are technically objects [ci skip] | Zachary Scott | 2014-12-29 | 1 | -2/+2 | |
| | ||||||
* | Rephrase Four Hashes of the Apocalypse [ci skip] | Zachary Scott | 2014-12-29 | 1 | -1/+1 | |
| | ||||||
* | Compare http request type with test equivalent methods, and application ↵ | Zachary Scott | 2014-12-29 | 1 | -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 Scott | 2014-12-29 | 1 | -1/+1 | |
| | | | | [ci skip] | |||||
* | Add example to get Errored test to pass in Testing guide [ci skip] | Zachary Scott | 2014-12-25 | 1 | -0/+13 | |
| | ||||||
* | warn about reading guides in GitHub | Xavier Noria | 2014-12-23 | 1 | -0/+2 | |
| | | | | References #18148. | |||||
* | Remove this section, it adds no real value [ci skip] | Zachary Scott | 2014-12-22 | 1 | -4/+0 | |
| | ||||||
* | Add subheadings for these sections [ci skip] | Zachary Scott | 2014-12-22 | 1 | -0/+4 | |
| | ||||||
* | I'm sorry but I would rather not link to a 7 year old blog post [ci skip] | Zachary Scott | 2014-12-22 | 1 | -2/+0 | |
| | ||||||
* | Remove this line since we are using Rake to run our tests [ci skip] | Zachary Scott | 2014-12-22 | 1 | -1/+1 | |
| | ||||||
* | s/are edited and rerun/required modifications [ci skip] | Zachary Scott | 2014-12-22 | 1 | -2/+2 | |
| | ||||||
* | document the return of `db:test:prepare`. Closes #18136. [ci skip] | Yves Senn | 2014-12-22 | 1 | -1/+10 | |
| | | | | | | This is a doc follow-up to #17739. /cc @zzak | |||||
* | Better explain number of assertions per test [ci skip] | Zachary Scott | 2014-12-22 | 1 | -1/+1 | |
| | ||||||
* | Remove duplicate description of the previous line [ci skip] | Zachary Scott | 2014-12-22 | 1 | -1/+1 | |
| | ||||||
* | Fix NOTE for method naming in Ruby and add intro sentence to next section. | Zachary Scott | 2014-12-22 | 1 | -1/+3 | |
| | | | | [ci skip] | |||||
* | Removed run-on sentence and replace with sectional comments [ci skip] | Zachary Scott | 2014-12-22 | 1 | -2/+2 | |
| | ||||||
* | Better explain how test() methods get defined and kill this run-on sentence. | Zachary Scott | 2014-12-22 | 1 | -2/+2 | |
| | | | | [ci skip] | |||||
* | We may only look at some of the methods available from TestCase [ci skip] | Zachary Scott | 2014-12-22 | 1 | -1/+1 | |
| | ||||||
* | Better explain what `test_helper.rb` is designed for [ci skip] | Zachary Scott | 2014-12-22 | 1 | -1/+1 | |
| | ||||||
* | Testing guide grammar fix | Jon Atack | 2014-12-21 | 1 | -1/+1 | |
| | | | [skip ci] | |||||
* | We will be using the application already created in the Getting Started guide. | Zachary Scott | 2014-12-20 | 1 | -4/+2 | |
| | | | | [ci skip] | |||||
* | Follow-up to d9710212 [skip ci] | Jon Atack | 2014-12-21 | 1 | -1/+1 | |
| | ||||||
* | Fixture data is accessible by a local method, and not a variable [ci skip] | Zachary Scott | 2014-12-20 | 1 | -2/+2 | |
| | ||||||
* | Shorten the explaination of this to fit on one line [ci skip] | Zachary Scott | 2014-12-20 | 1 | -1/+1 | |
| | ||||||
* | s/folder/directory [ci skip] | Zachary Scott | 2014-12-20 | 1 | -7/+7 | |
| | ||||||
* | "In PostgreSQL, just superusers.." => "In PostgreSQL, only superusers.." | Zachary Scott | 2014-12-20 | 1 | -1/+1 | |
| | | | | [ci skip] | |||||
* | Make sure this section is rendered as a `NOTE` and remove redundant sentence. | Zachary Scott | 2014-12-20 | 1 | -5/+1 | |
| | | | | [ci skip] | |||||
* | Add note about the association between the two fixture files and how they're ↵ | Zachary Scott | 2014-12-20 | 1 | -0/+2 | |
| | | | | | | connection. [ci skip] | |||||
* | Remove YAML implementation detail, as we're not trying to document all of | Zachary Scott | 2014-12-20 | 1 | -1/+1 | |
| | | | | YAML's behavior in this guide. [ci skip] | |||||
* | Remove use of "very" [ci skip] | Zachary Scott | 2014-12-20 | 1 | -1/+1 | |
| | ||||||
* | Describe the mailer and helpers directories which are generated by `rails new`. | Zachary Scott | 2014-12-20 | 1 | -1/+1 | |
| | | | | [ci skip] | |||||
* | Update comment regarding test environment with help from @matthewd [ci skip] | Zachary Scott | 2014-12-20 | 1 | -1/+3 | |
| | ||||||
* | Adding a tip in the guides about possible database permission problems on | andrey.nering@gmail.com | 2014-12-09 | 1 | -0/+2 | |
| | | | | | | loading fixtures to the database. Reference #17542 | |||||
* | [Testing guide] Using "Fixtures API" consistently | Prathamesh Sonpatki | 2014-11-30 | 1 | -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. | |||||
* | [Testing guide] Use "Fixtures API" instead of "fixture api". | Prathamesh Sonpatki | 2014-11-30 | 1 | -1/+1 | |
| | ||||||
* | Simplify and fix grammar | Jon Atack | 2014-11-14 | 1 | -5/+4 | |
| | | | [skip ci] | |||||
* | [CI SKIP] Corrections to testing guide. | Guo Xiang Tan | 2014-11-14 | 1 | -2/+2 | |
| | | | | Partially revert https://github.com/rails/rails/commit/c31e638a37946a120f6dbf207127d36beea5ab85. | |||||
* | [ci skip] Remove deprecated testing tasks | Sandip Ransing | 2014-11-14 | 1 | -4/+2 | |
| | | | | | This has changed recently and so rake test:all and rake test:all:db are deprecated. | |||||
* | [ci skip] Improve upon testing tasks guide | Sandip Ransing | 2014-11-14 | 1 | -3/+5 | |
| | | | | Add missing testing tasks and also improve upon tasks descriptions | |||||
* | [ci skip] Capybara added to other testing approaches | Sandip Ransing | 2014-11-14 | 1 | -0/+1 | |
| | ||||||
* | [ci skip] Add one more example to routing testing, and highlight association | Sandip Ransing | 2014-11-13 | 1 | -2/+6 | |
| | | | | name keywords | |||||
* | Merge pull request #17348 from DavidGeukers/rake_test_all | David Heinemeier Hansson | 2014-11-12 | 1 | -3/+2 | |
|\ | | | | | simplify rake test vs rake test:all | |||||
| * | Simplify rake test vs rake test:all | David Geukers | 2014-11-10 | 1 | -3/+2 | |
| | | | | | | | | Renames `rake test:all` to `rake test` by changing old `rake test:run` to previous version of `rake test:all`. Removes old definition of `rake test`. Also renames `rake test:all:db` to `rake test:db` and deprecates `rake test:all` & `rake test:all:db` | |||||
* | | Merge pull request #17476 from robin850/job-testing | Robin Dupret | 2014-11-08 | 1 | -0/+62 | |
|\ \ | | | | | | | Add a section about job testing [ci skip] | |||||
| * | | Add a section about job testing [ci skip] | Ryan Selk | 2014-11-02 | 1 | -0/+62 | |
| |/ | | | | | | | | | | | | | | | * Cover lower level job testing (assertions about the execution of the job itself). * Add a table with the custom assertions provided by Active Job's `TestHelper` module. * Add an example testing job queuing inside a model | |||||
* | | Guides: Corrected name for assigns key [ci skip] | Jimmy Petersen | 2014-11-07 | 1 | -1/+1 | |
| | | | | | | | | | | - Integration test example is now using 'articles' name for both path and assigns key. | |||||
* | | Merge pull request #17040 from clyfe/patch-1 | Rafael Mendonça França | 2014-10-31 | 1 | -2/+4 | |
|\ \ | |/ |/| | Explicit route test class |