aboutsummaryrefslogtreecommitdiffstats
path: root/railties/test/application/test_runner_test.rb
Commit message (Collapse)AuthorAgeFilesLines
* Prefer Minitest's location for test failures.Kasper Timm Hansen2015-11-121-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | When running tests, the Rails test runner would report the start of the test method as the test failure. For this test: ```ruby 1 require 'test_helper 2 3 class BunnyTest < ActiveSupport::TestCase 4 test "something failing" do 5 assert false, 'This failed' 6 end 7 end ``` The runner outputs 5 instead of 4: ``` ............................................F This failed bin/rails test test/models/bunny_test.rb:5 ........ ```
* Refactor create_test_file to take a pass option.Kasper Timm Hansen2015-10-071-31/+7
| | | | Lets us cut the verbose and straight up duplicated setup in 3 tests down to one line.
* Hide Minitest's aggregated results if outputting inline.Kasper Timm Hansen2015-10-071-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We'd see the failures and errors reported after the run, which is needless, when we've already reported them. Turns: ``` .......................................S....................F This failed bin/rails test test/models/bunny_test.rb:14 .... Finished in 0.100886s, 1020.9583 runs/s, 1001.1338 assertions/s. 2) Failure: BunnyTest#test_something_failing [/Users/kasperhansen/Documents/code/collection_caching_test/test/models/bunny_test.rb:15]: This failed 103 runs, 101 assertions, 1 failures, 0 errors, 1 skips You have skipped tests. Run with --verbose for details. ``` Into: ``` ...................S.......................................F This failed bin/rails test test/models/bunny_test.rb:14 ...................... Finished in 0.069910s, 1473.3225 runs/s, 1444.7143 assertions/s. 103 runs, 101 assertions, 1 failures, 0 errors, 1 skips ```
* Add fail fast to test runner.Kasper Timm Hansen2015-09-291-0/+15
| | | | | Passing `--fail-fast` to the test runner will now abort the test run on the first failure. The run continues on any unexpected errors.
* Add inline failure reporting to test runner.Kasper Timm Hansen2015-09-281-0/+15
| | | | | | | | | Any failures or errors will be reported inline during the run by default. Skipped tests will be reported if run in verbose mode. Any result is output with failure messages and a rerun snippet for that test. Rerun snippets won't be output after a run, unless `--defer-output` is passed.
* raise LoadError when a non-existent file or directory is specified to the ↵yuuji.yaginuma2015-09-071-0/+5
| | | | | | | | test runner Currently, if a file or directory that does not exist was specified in the test runner, that argument is ignored. This commit has been modified to cause an error if there is no file or directory.
* tests, railties tests should use `bin/` executables when possible.Yves Senn2015-06-301-1/+1
| | | | | We recommend using the `bin/` executables in our docs and guides. Let's make sure that our tests execute the same code path.
* Improve test runner's Minitest integration.Kasper Timm Hansen2015-06-041-25/+140
| | | | | | | | | | | This also adds free mix and matching of directories, files and lines filters. Like so: bin/rails test models/post_test.rb test/integration models/person_test.rb:26 You can also mix in a traditional Minitest filter: bin/rails test test/integration -n /check_it_out/
* `-p`, `--pattern` to run tests using a pattern.Yves Senn2015-03-181-2/+1
|
* use `bin/rails t` runner in `test_runner_test.rb`.Yves Senn2015-03-181-24/+18
|
* tests, use `capture` instead of custom `redirect_stderr` helper.Yves Senn2015-01-301-12/+2
|
* Add `test:jobs` taskyuuji.yaginuma2014-09-151-3/+14
|
* Updates to make rails 4 happy with minitest 5:Ryan Davis2013-05-061-10/+10
| | | | | | | | | | + Namespace changes, overhaul of runners. + Internal ivar name changes - Removed a logger globally applied to tests that spew everywhere?!? + Override Minitest#__run to sort tests by name. + Reworked testing isolation to work with the new cleaner architecture. - Removed a bunch of tests that just test minitest straight up. I think these changes were all merged to minitest 4 a long time ago. - Minor report output differences.
* add integration test for shorthand rake testsAaron Patterson2013-04-051-0/+7
|
* extract test info from the command line and set up the test taskAaron Patterson2013-04-051-1/+22
|
* removing `rails test`, updating docs to show how to use `rake test`Aaron Patterson2013-04-051-6/+0
|
* do not blow away the test database on every runAaron Patterson2013-04-051-10/+0
|
* switch the testing tests to use rakeAaron Patterson2013-04-031-20/+23
|
* apps that depend on active record should load fixturesAaron Patterson2013-04-031-7/+0
|
* Replace assert_(no_)match args from regexps to strings to remove warningsCarlos Antonio da Silva2013-03-111-40/+40
| | | | | | Using regexps as arguments without parentheses end up raising: warning: ambiguous first argument; put parentheses or even spaces
* Make sure that the test case is run under test envPrem Sichanugrist2013-03-111-1/+17
| | | | | | * Unset $RAILS_ENV that got set by abstract_unit to trigger the default. * split out environment setting since Ruby 1.9.3 doesn't support inline ENV setting.
* Fix test failure introduced in 3ed41e57Prem Sichanugrist2013-03-111-5/+3
| | | | I forgot to run the test suit after changing the task name. :bomb:
* Make sure that `rails test` load test in test envPrem Sichanugrist2013-03-091-1/+44
|
* Improve wording for rails test commandDalibor Nasevic2013-03-091-8/+8
|
* Load fixtures only when running suites, or `-f`Prem Sichanugrist2013-03-091-0/+51
| | | | | | * `rails test -f` will run the test suites with all fixtures loaded * New application will now generated without `fixtures :all` line enabled by default.
* Add support for MiniTest flags in TestRunnerPrem Sichanugrist2013-03-091-0/+21
| | | | | Any flags that got set will be passed through to MiniTest::Unit.runner, such as `-n`, `-s-, and `-v`.
* Add `rails test` command to run the test suitePrem Sichanugrist and Chris Toomey2013-03-091-0/+183
To run the whole test suite: $ rails test To run the test file(s): $ rails test test/unit/foo_test.rb [test/unit/bar_test.rb ...] To run the test suite $ rails test [models,helpers,units,controllers,mailers,...] For more information, see `rails test --help`. This command will eventually replacing `rake test:*`, and `rake test` command will actually invoking `rails test` instead.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-16 18:43:12 +0000