[lnkForumImage]
TotalShareware - Download Free Software

Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

comp.lang.ruby

Test::Unit Difficulties

Trans

3/5/2005 5:11:00 PM

Hi--

I working on the test suite for Ruby Facets, a collection of pure-ruby
core extensions. Trouble is a few of the extension methods conflict
with each other --not being meant to be require together. So I can't
just require them all up at once and expect the tests to work.

So my first question is: is it possible to unrequire? If not then how
does one run fully independent tests using Test::Unit while still
accumulating the test results?

Secondly, when using Test::Unit on multiple tests, using multiple
requires, I'm not getting any test results at all. The Test::Unit docs
say this should work. And each individual test does work when run by
itself. So I'm not sure what the problem is. Here's a copy of the
shell:

ruby -e0 -r"test/unit" -r"test/nil/tc_nil" -r"test/file/tc_file" -r"test/hash/tc_hash" -r"test/hash/tc_each" -r"test/hash/tc_slice" -r"test/proc/tc_proc" -r"test/time/tc_time" -r"test/fileutils/tc_whereis" -r"test/fileutils/tc_head&tail" -r"test/fileutils/tc_which" -r"test/fileutils/tc_wc" -r"test/array/tc_brackets" -r"test/array/tc_array" -r"test/class/tc_class" -r"test/float/tc_float" -r"test/range/tc_range" -r"test/comparable/tc_comparable" -r"test/matchdata/tc_matchdata" -r"test/kernel/tc_warn_with_line" -r"test/kernel/tc_kernel" -r"test/module/tc_redef" -r"test/module/tc_module" -r"test/module/tc_memoize" -r"test/module/tc_methods" -r"test/object/tc_object" -r"test/object/tc_constant" -r"test/object/tc_with_accessor" -r"test/object/tc_supers" -r"test/enumerable/tc_enumerable" -r"test/regexp/tc_regexp" -r"test/string/tc_unix_crypt" -r"test/string/tc_string" -r"test/string/tc_margin" -r"test/string/tc_fuzzy_match" -r"test/symbol/tc_symbol" -r"test/numeric/tc_numeric" -r"test/ostruct/tc_ostruct" -r"test/integer/tc_integer"
Loaded suite .
Started

Finished in 0.000483 seconds.

0 tests, 0 assertions, 0 failures, 0 errors


Any suggestions are greatly appreciated.

Thanks,
T.