This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
commit e931012287df0bca83cae04d95c2e0835ae08758
tree 46af916792dbd3a74883b4e1b572dd432cee4a59
parent 5d3712a81e502f46b2745d238d9bb76fcdb31f5b
tree 46af916792dbd3a74883b4e1b572dd432cee4a59
parent 5d3712a81e502f46b2745d238d9bb76fcdb31f5b
- actionpack/test/abstract_unit.rb
- activemodel/test/test_helper.rb
- activesupport/lib/active_support/test_case.rb
- activesupport/lib/active_support/testing/mocha_minitest_adapter.rb
- activesupport/test/abstract_unit.rb
- railties/test/abstract_unit.rb
... |
... |
|
... |
... |
|












Is mocha 0.9.3 even out yet? Rubyforge says the latest is 0.9.2.
http://github.com/jeremy/mocha/tree/master
Do you need me to release current Mocha HEAD as 0.9.3; or is this a typo; or are you expecting other changes in Mocha 0.9.3?
If you’re ready for 0.9.3, by all means :)
Otherwise, this is just saying that edge Rails needs the next release of Mocha for MiniTest compatibility.
Won’t this code in test_case.rb cause a problem when the mocha gem is localized? In that case, the require ‘mocha’ statement will never be reached . I think this code snippet in test_case.rb
Should be change to:
Sure, could you work up a patch and post to lighthouse?