aboutsummaryrefslogtreecommitdiffstats
path: root/activesupport/lib/active_support/testing
Commit message (Collapse)AuthorAgeFilesLines
* determine_constant_from_test_name does not swallow NoMethodErrors [Yves Senn]Xavier Noria2013-03-281-0/+2
|
* Bump up minitest dependency and remove our own reinvented version of ↵Akira Matsuda2013-02-191-37/+1
| | | | ParallelEach
* 'minitest/parallel_each' might not always be availableAkira Matsuda + Koichi Sasada2013-01-291-1/+4
|
* Needs to explicitly require 'minitest/parallel_each'Akira Matsuda + Koichi Sasada2013-01-291-0/+2
| | | | Minitest has changed to require this since https://github.com/seattlerb/minitest/commit/728054b
* The test setup is not threadsafe. Wrap in a mutex.Jon Leighton2013-01-181-3/+7
|
* MiniTest already defines a ParallelEach classJon Leighton2013-01-181-23/+27
| | | | | This may or may not fix the intermittent railties failures we've been seeing on the CI with Ruby 2.0. We'll see.
* extract PerformanceTest into rails-performance_tests gemYves Senn2013-01-104-672/+0
|
* deprecate `assert_blank` and `assert_present`.Yves Senn2013-01-051-0/+2
| | | | | They don't add any benefits over `assert object.blank?` and `assert object.present?`
* added marshal_load and marshal_dump for ProxyTestResult. Behavior of ↵SHIBATA Hiroshi2013-01-051-2/+10
| | | | method_missing with Marshal.dump and Marshal.load is changing in ruby 2.0.0 later.
* Add active_support/testing/autorunRafael Mendonça França2012-12-311-0/+5
| | | | | minitest/autorun load minitest/spec polluting the global namespace with the DSL that we don't want on Rails
* Revert "minitest provides "it" and "describe""Rafael Mendonça França2012-12-311-0/+40
| | | | | | | | | | This reverts commit 22bc12ec374b8bdeb3818ca0a3eb787dd3ce39d8. REASON: We will remove the MiniTest::Spec from Rails and we need these methods again Conflicts: activesupport/lib/active_support/test_case.rb
* Introduce assert_not to replace 'assert !foo'Jeremy Kemper2012-12-281-0/+16
|
* Make test logs easier to read.Jeremy Kemper2012-12-261-11/+10
| | | | | | Tagging every message in tests makes the logs really wide. It's great for grepping, but annoying to open in an editor or a narrow terminal. Try out a different approach: spit out a heading before each test.
* nodoc AS::Testing::ConstantLookup::ClassMethods [ci skip]Carlos Duclos2012-12-011-1/+1
|
* nodoc AS::Testing::Pending because is deprecated [ci skip]Carlos Duclos2012-12-011-2/+2
|
* Properly deprecate #pending from AS::TestCaseCarlos Antonio da Silva2012-11-181-8/+2
| | | | Check https://github.com/rails/rails/pull/4575#issuecomment-5765575.
* Revert "Merge pull request #4575 from carlosantoniodasilva/remove-test-pending"Carlos Antonio da Silva2012-11-181-0/+20
| | | | | | | | | This reverts commit 1620df78dff527b4fa3f7b204fa05d1b630aae17, reversing changes made to 2d000328dfc0d4b297fb4bdcebc9af6c2fb559dc. Conflicts: activesupport/CHANGELOG.md activesupport/lib/active_support/test_case.rb
* Simplify code by taking advantage of latest mocha (v0.13.0).James Mead2012-11-121-22/+0
| | | | | | | | | | | | | | | | | | | | | | | | | This only works with mocha v0.13.0 or later. Note that this also fixes a few subtle bugs present in the current implementation :- * Mocha was raising a `MiniTest::Assertion` instead of a `Mocha::ExpectationError` as intended. The latter is not recognized by MiniTest as an assertion failure and so it is recorded as a test *error*, not a test *failure* as it ought to. This leads to potentially confusing output in the test results. * Mocha verification should happen as part of the test. The verification of expectations is equivalent to a set of assertions. These assertions should happen as *part of* the test so that they have a chance to cause the test to fail, and not just as part of the teardown. Also if an assertion fails during the test, then there is no need to verify expectations, because only the first assertion failure is normally reported and all subsequent bets are off. * Expectation verification should be counted as an assertion. Mocha cannot record each expectation verification as an assertion, because we weren't passing in an assertion counter to `#mocha_verify`.
* mocha_standalone is now deprecated. Switch to mocha/api.Jeremy Kemper2012-11-051-1/+1
|
* Remove AS::Concern extension from Testing::TaggedLoggingCarlos Antonio da Silva2012-11-051-4/+0
|
* some ruby interpreters don't have ruby-prof so just skip the testsAaron Patterson2012-10-181-1/+1
| | | | rather than exiting the process.
* Tests tag the Rails log with the current test class and test caseJeremy Kemper2012-09-261-0/+30
|
* Add missing inflector dependencyMike Moore2012-09-251-3/+2
|
* Create ActiveSupport::Testing::ConstantLookupMike Moore2012-09-241-0/+53
| | | | | AS::TC::ConstantLookup walks the test's name to find the constant it is describing. This additional lookup logic is needed to better support minitest's spec DSL.
* update AS/notifications and AS/testing docs [ci skip]Francesco Rodriguez2012-09-142-7/+9
|
* deprecate `describe` without a block.Aaron Patterson2012-07-091-22/+0
| | | | | minitest/spec provides `describe`, so deprecate the rails version and have people use the superclass version
* we still need `describe` as the implementation differs from minitestAaron Patterson2012-07-081-0/+22
|
* minitest provides "it" and "describe"Aaron Patterson2012-07-081-40/+0
| | | | Remove rails implementation of describe, alias "test" to "it"
* Kill not used constant since removal of runner methodCarlos Antonio da Silva2012-07-031-9/+0
| | | | Runner method was removed in ada571bfcdbad669ae43a4dd18277ef227680a0b.
* remove the runner method copied from minitestAaron Patterson2012-07-031-20/+7
|
* hook mocha in through m/t before_setup, after_teardown hooksAaron Patterson2012-07-032-7/+22
|
* add :nodoc: to internal implementations [ci skip]Francesco Rodriguez2012-06-222-2/+2
|
* Merge branch 'master' of github.com:lifo/docrailsVijay Dev2012-06-221-23/+34
|\
| * fixes a few mistakes in api docs [ci skip]Vijay Dev2012-06-221-1/+1
| |
| * update AS::Testing::Assertions docsFrancesco Rodriguez2012-06-191-21/+32
| |
| * fix typo [ci skip]Francesco Rodriguez2012-06-191-2/+2
| |
* | Run the logger tests in isolationRafael Mendonça França2012-06-191-1/+1
| |
* | CORES needs to be a integerRafael Mendonça França2012-06-191-1/+1
| |
* | run railties tests in parallel, default to 2 coresAaron Patterson2012-06-191-0/+39
|/
* Eliminate dependency on Rails::VERSION::STRINGAndrew White2012-06-051-18/+23
| | | | | | To facilitate the use of ActiveSupport::Testing::Performance outside of a Rails application conditionally check for the presence of Rails::VERSION::STRING before including it in the environment string.
* Reduce warning messages when running Active Support testsAndrew White2012-05-311-0/+5
| | | | Eliminate the warnings generated by redefining methods and constants.
* Merge pull request #6525 from freerange/minitest-passthrough-exceptionsJosé Valim2012-05-291-0/+12
|\ | | | | Exceptions like Interrupt & NoMemoryError should not be rescued in tests.
| * Avoid dependency on MiniTest::Unit::TestCase::PASSTHROUGH_EXCEPTIONS.James Mead2012-05-291-2/+10
| |
| * Exceptions like Interrupt should not be rescued.James Mead2012-05-281-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Neither Test::Unit nor MiniTest rescue exceptions like Interrupt or NoMemoryError, but ActiveSupport::Testing::SetupAndTeardown#run which overrides MiniTest::Unit::TestCase#run rescues them. Rescuing an Interrupt exception is annoying, because it means when you are running a lot of tests e.g. when running one of the rake test tasks, you cannot break out using ctrl-C. Rescuing exceptions like NoMemoryError is foolish, because the most sensible thing to happen is for the process to terminate as soon as possible. This solution probably needs some finessing e.g. I'm not clear whether the assumption is that only MiniTest is supported. Also early versions of MiniTest did not have this behaviour. However, hopefully it's a start. Integrating with Test::Unit & MiniTest has always been a pain. It would be great if both of them provided sensible extension points for the kind of things that both Rails and Mocha want to do.
* | decoupling activesupport performance testing from actionview and adding testsAndrew Mutz2012-05-281-4/+4
|/
* reverting decoupling of NumberHelper from safe_join and adding tests for ↵Andrew Mutz2012-05-181-0/+1
| | | | escaping of delimiters and separators
* Remove dependency on safe_join from number helpersCarlos Antonio da Silva2012-05-131-3/+2
| | | | Introduced in 0f848dd54911f0e15c5c3aceabf09582cc6eab16.
* Need to include "OutputSaftyHelper" here to preventArun Agrawal2012-05-131-0/+1
| | | | | `number_with_delimiter': undefined method `safe_join' for #<ActiveSupport::Testing::Performance::Metrics::Objects
* Fixed ruby-prof changes and let's use latest ruby-prof now.Arun Agrawal2012-05-131-1/+1
|
* Remove key argument from run_callbacks to fix buildFrancesco Rodriguez2012-05-101-1/+1
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 20:10:19 +0000