On Thursday 06 April 2006 14:09, Kyle Shank wrote:
Did you check this into HEAD?
I did.
On 4/5/06, David Corbin [EMAIL PROTECTED] wrote:
It's fixed. I don't understand why I see it in RDT, and not when using
the console test runner, but I think my fix is a good one. And I really
don't
On Wednesday 05 April 2006 08:29 pm, David Corbin wrote:
On Wednesday 05 April 2006 07:27 pm, David Corbin wrote:
On Wednesday 05 April 2006 07:20 pm, David Corbin wrote:
On Wednesday 05 April 2006 06:41 pm, you wrote:
Exactly what 'parameters' are specified in the test launch?
I
All,
I think an 0.8.0 release (at least a release candidate) is do-able.
We already have a lot of functionality since the 0.7.0 release, and
it's been working fine for me (I patched bugs with the new browsing
stuff locally, but until just now SF.net's CVS was down so I just
checked them
The RemoteTestRunner issue is a result of the new Rails integration
testing. They define a default_test in
ActionController::IntegrationTest that gets picked up by the test
runner because it extends Test::Unit::TestCase. What happens is that
if there are 9 real tests that all pass the bar will
