On May 4, 2011, at 05:08 , anoiaque wrote:
> Why both minitest and testunit modules are so tied to output in the code ...
> Why is there no class/instance method with which i can get result as an
> object (~ Minitest::Unit.run() =>
> )
>
> Why must i hack theses modules(even if its quite easy
As we say in french "Nous ne sommes jamais mieux servis que
par nous-mêmes" .
In my main project, i've made a module which respond to what
i want :
Get an object (TestResult object) after each test (it is yielded after
each test and return an object of class Error , Failure, Error or Success)
an
Hi,
Minitest doesn't have a really clean way of doing what you want, but it does
have a simple way. If you look at minitest/pride:
https://github.com/seattlerb/minitest/blob/master/lib/minitest/pride.rb
It implements an alternative output format for minitest that you could copy and
the
Hi,
Why both minitest and testunit modules are so tied to output in the code ...
Why is there no class/instance method with which i can get result as an object
(~ Minitest::Unit.run() => )
Why must i hack theses modules(even if its quite easy with ruby) to get result
as an object i can work wit
