Unit testing with ruby1.9.x

Ruby
1

Built ruby from a recent svn. Builds fine and works.

ruby19jx --version
ruby 1.9.2dev (2009-03-18) [i686-linux]

Now for some unit testing;

gem install ‘test-unit’ --remote

run a test on some code;

ruby19jx proj/code/rb/projects/virt/vz/test/test_vz001.rb
ruby 1.9.2dev (2009-03-18) [i686-linux]
/home/jayeola/ix/lib/ruby19jx/gems/1.9.1/gems/test-unit-2.0.2/lib/test/unit/autorunner.rb:1:
warning: loading in progress, circular require considered harmful -
/home/j
ayeola/ix/lib/ruby19jx/gems/1.9.1/gems/test-unit-2.0.2/lib/test/unit.rb
FE

the autorunner? Am I to require unit/test2.x or something?

–
John M.
07739 171 531
MSc (DIC)

Timezone: GMT

2

On Mar 26, 2009, at 14:08, john maclean wrote:

Built ruby from a recent svn. Builds fine and works.

ruby19jx --version
ruby 1.9.2dev (2009-03-18) [i686-linux]

Now for some unit testing;

gem install ‘test-unit’ --remote

What’s wrong with minitest that ships with 1.9?

3

2009/3/26 Eric H. [email protected]:

What’s wrong with minitest that ships with 1.9?

Uh, can you point me to some useful docs? Not come across this module
before and I see no obvious docs, (ri or gem server). /me is surprised
about this one!

–
John M.
07739 171 531
MSc (DIC)

Timezone: GMT

4

On Mar 26, 2009, at 15:05, john maclean wrote:

gem install ‘test-unit’ --remote

What’s wrong with minitest that ships with 1.9?

Uh, can you point me to some useful docs? Not come across this module
before and I see no obvious docs, (ri or gem server). /me is surprised
about this one!

It’s just like 1.8’s test unit, but with some changes to the assertions:

$ ri MiniTest::Assertions
-------------------------------------------- Class: MiniTest::Assertions
[no description]

Instance methods:
_assertions, _assertions=, assert, assert_block, assert_empty,
assert_equal, assert_in_delta, assert_in_epsilon, assert_includes,
assert_instance_of, assert_kind_of, assert_match, assert_nil,
assert_operator, assert_raises, assert_respond_to, assert_same,
assert_send, assert_throws, capture_io, exception_details, flunk,
message, mu_pp, pass, refute, refute_empty, refute_equal,
refute_in_delta, refute_in_epsilon, refute_includes,
refute_instance_of, refute_kind_of, refute_match, refute_nil,
refute_operator, refute_respond_to, refute_same, skip

See also the minitest gem.

5

2009/3/27 Tom C. [email protected]:

discussion in various books which take up Ruby 1.9. The library author has
Bellingham, Washington, U.S.A: (360) 920-1226
<< [email protected] >> (email)
<< TomCloyd.com >> (website) << sleightmind.wordpress.com >> (mental health
weblog)

I think I’m going to stick with test-unit from gems. Couldn’t really
follow the ri docs for minitest, although there are a few snippets on
the net.

gem19jx list test-unit --remote

*** REMOTE GEMS ***

test-unit (2.0.2)
test-unit-ext (0.5.0)
test-unit-full (0.0.1)
test-unit-mock (0.30)
test-unit-runner-fox (0.0.1)
test-unit-runner-gtk2 (0.0.1)

–
John M.
07739 171 531
MSc (DIC)

Timezone: GMT

6

john maclean wrote:

At the risk of stating what is obvious to some and may not be to all,
minitest is now the default testing library supplied with 1.9, replacing
the previously supplied Test::Unit library. I am informed that there one
can easily obtain the same functionality with minitest - but I know
essentially nothing about this, and there seems to be no documentation,
outside of discussion in various books which take up Ruby 1.9. The
library author has said that the code is easy enough to read that that
is good documentation.

Hope this helps.

Tom

–

Tom C., MS MA, LMHC - Private practice Psychotherapist
Bellingham, Washington, U.S.A: (360) 920-1226
<< [email protected] >> (email)
<< TomCloyd.com >> (website)
<< sleightmind.wordpress.com >> (mental health weblog)