S
Simon Strandgaard
using the Rubyunit distributed with Ruby-1.8.0-preview3.
I have an 'assert_exception' that fails.. ok.
The filename rubyunit(test::unit) is outputting is annoying.
Wouldn't it be an idea to output the file in which the problem actual is
located in ?
Yes I know I could use grep
Started
test_all.rb: unrecognized option `--badbadbad'
...........F...............................................................
...........................................................................
...........................................................................
........................................................
Finished in 1.14403 seconds.
1) Failure!!!
TestBuffer#test_joinline3 [/home/neoneye/stow/ruby18_r3/lib/ruby/1.8/runit/assert.rb:56]:
<BufferTop> exception expected but none was thrown
277 tests, 948 assertions, 1 failures, 0 errors
BTW: at some time I think I will convert the code to 'test::unit' ?
I have an 'assert_exception' that fails.. ok.
The filename rubyunit(test::unit) is outputting is annoying.
Wouldn't it be an idea to output the file in which the problem actual is
located in ?
Yes I know I could use grep
Loaded suite Unnamed TestSuiteruby test_all.rb
Started
test_all.rb: unrecognized option `--badbadbad'
...........F...............................................................
...........................................................................
...........................................................................
........................................................
Finished in 1.14403 seconds.
1) Failure!!!
TestBuffer#test_joinline3 [/home/neoneye/stow/ruby18_r3/lib/ruby/1.8/runit/assert.rb:56]:
<BufferTop> exception expected but none was thrown
277 tests, 948 assertions, 1 failures, 0 errors
BTW: at some time I think I will convert the code to 'test::unit' ?