From noreply at rubyforge.org  Wed Jun  2 10:47:41 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Wed,  2 Jun 2010 10:47:41 -0400 (EDT)
Subject: [test-unit-tracker] [ test-unit-Bugs-28267 ] global config file
	ignored
Message-ID: <20100602144741.E76F81858317@rubyforge.org>

Bugs item #28267, was opened at 2010-06-02 07:47
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=28267&group_id=5650

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: global config file ignored

Initial Comment:
Hi,

Looks like a typo in autorunner.rb is causing the global .test-unit.yml file to be ignored.

--- autorunner.orig	2010-06-02 08:44:08.633170542 -0600
+++ autorunner.rb	2010-06-02 08:45:12.006490264 -0600
@@ -342,7 +342,7 @@
       end
 
       def global_config_file
-        File.expand_path("~/.test-unit.xml")
+        File.expand_path("~/.test-unit.yml")
       rescue ArgumentError
         nil
       end

Regards,

Dan

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=28267&group_id=5650

From noreply at rubyforge.org  Thu Jun  3 06:51:41 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Thu,  3 Jun 2010 06:51:41 -0400 (EDT)
Subject: [test-unit-tracker] [ test-unit-Bugs-28267 ] global config file
	ignored
Message-ID: <20100603105141.E1857185836C@rubyforge.org>

Bugs item #28267, was opened at 2010-06-02 23:47
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=28267&group_id=5650

Category: None
Group: None
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: global config file ignored

Initial Comment:
Hi,

Looks like a typo in autorunner.rb is causing the global .test-unit.yml file to be ignored.

--- autorunner.orig	2010-06-02 08:44:08.633170542 -0600
+++ autorunner.rb	2010-06-02 08:45:12.006490264 -0600
@@ -342,7 +342,7 @@
       end
 
       def global_config_file
-        File.expand_path("~/.test-unit.xml")
+        File.expand_path("~/.test-unit.yml")
       rescue ArgumentError
         nil
       end

Regards,

Dan

----------------------------------------------------------------------

>Comment By: Kouhei Sutou (kou)
Date: 2010-06-03 19:51

Message:
!!!
You're right!

I've fixed it in trunk.
Thanks!!!

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=28267&group_id=5650

From noreply at rubyforge.org  Sat Jun  5 12:33:57 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sat,  5 Jun 2010 12:33:57 -0400 (EDT)
Subject: [test-unit-tracker] [ test-unit-Feature Requests-28279 ] Nicer
	output for true vs false
Message-ID: <20100605163357.5A2CE1858362@rubyforge.org>

Feature Requests item #28279, was opened at 2010-06-05 09:33
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21859&aid=28279&group_id=5650

Category: None
Group: None
Status: Open
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: Nicer output for true vs false

Initial Comment:
Hi,

As of test-unit 2.0.9 a true vs false result looks like this:

<true> expected but was
<false>

diff:
? tru e
? fals

Is there any chance of making a specific check for boolean values so that it looks like this?

diff:
? true
? false

I tried to make this modification myself, but diff.rb is quite difficult to follow.

Regards,

Dan

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21859&aid=28279&group_id=5650

From noreply at rubyforge.org  Sun Jun  6 01:17:18 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun,  6 Jun 2010 01:17:18 -0400 (EDT)
Subject: [test-unit-tracker] [ test-unit-Feature Requests-28279 ] Nicer
	output for true vs false
Message-ID: <20100606051718.CD3E91858351@rubyforge.org>

Feature Requests item #28279, was opened at 2010-06-06 01:33
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21859&aid=28279&group_id=5650

Category: None
Group: None
>Status: Closed
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: Nicer output for true vs false

Initial Comment:
Hi,

As of test-unit 2.0.9 a true vs false result looks like this:

<true> expected but was
<false>

diff:
? tru e
? fals

Is there any chance of making a specific check for boolean values so that it looks like this?

diff:
? true
? false

I tried to make this modification myself, but diff.rb is quite difficult to follow.

Regards,

Dan

----------------------------------------------------------------------

>Comment By: Kouhei Sutou (kou)
Date: 2010-06-06 14:17

Message:
Please use assert_true or assert_false for it.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21859&aid=28279&group_id=5650

From noreply at rubyforge.org  Sat Jun 12 20:10:47 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sat, 12 Jun 2010 20:10:47 -0400 (EDT)
Subject: [test-unit-tracker] [ test-unit-Feature Requests-28279 ] Nicer
	output for true vs false
Message-ID: <20100613001047.5F48A185837D@rubyforge.org>

Feature Requests item #28279, was opened at 2010-06-05 09:33
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21859&aid=28279&group_id=5650

Category: None
Group: None
Status: Closed
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: Nicer output for true vs false

Initial Comment:
Hi,

As of test-unit 2.0.9 a true vs false result looks like this:

<true> expected but was
<false>

diff:
? tru e
? fals

Is there any chance of making a specific check for boolean values so that it looks like this?

diff:
? true
? false

I tried to make this modification myself, but diff.rb is quite difficult to follow.

Regards,

Dan

----------------------------------------------------------------------

>Comment By: Daniel Berger (djberg96)
Date: 2010-06-12 17:10

Message:
Oh, I see. Ok.

Alright, now about nicer diff output vs nil?

  1) Failure:
test_getprotbynumber_result_not_expected(TC_Net_Proto)
[test/test_net_proto.rb:48]:
<nil> expected but was
<"hip">

# This doesn't look nice.
diff:
? n il 
? "h p"

Regards,

Dan

----------------------------------------------------------------------

Comment By: Kouhei Sutou (kou)
Date: 2010-06-05 22:17

Message:
Please use assert_true or assert_false for it.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21859&aid=28279&group_id=5650

From noreply at rubyforge.org  Sun Jun 20 14:44:37 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 20 Jun 2010 14:44:37 -0400 (EDT)
Subject: [test-unit-tracker] [ test-unit-Bugs-28312 ] test-unit's own tests
	fail on jruby
Message-ID: <20100620184437.7446A1858356@rubyforge.org>

Bugs item #28312, was opened at 2010-06-20 20:44
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=28312&group_id=5650

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Hans de Graaff (graaff)
Assigned to: Nobody (None)
Summary: test-unit's own tests fail on jruby

Initial Comment:
When trying to run the test-unit test suite on jruby I get the following test failures. The tests pass fine on ruby 1.8 and ruby enterprise edition.

  1) Failure:
test_assert_alias_method(Test::Unit::TC_Assertions)
    [/var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:19:in `check'
     /var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:55:in `check_assertions'
     /var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:82:in `check_fails'
     /var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:1146:in `test_assert_alias_method']:
Should have the correct message.
<"<#<Object:0x42bb0406>>.nonexistent doesn't exist\n(Class: <Object>)"> expected but was
<"<#<Object:0x30>>.nonexistent doesn't exist\n(Class: <Object>)">

  2) Omission: encoding test is for Ruby >= 1.9
test_assert_equal_with_different_encoding(Test::Unit::TC_Assertions)
/var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:319:in `test_assert_equal_with_different_encoding'

  3) Failure:
test_assert_in_delta(Test::Unit::TC_Assertions)
    [/var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:19:in `check'
     /var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:55:in `check_assertions'
     /var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:82:in `check_fails'
     /var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:842:in `test_assert_in_delta']:
Should have the correct message.
<"The arguments must respond to to_f; the first float did not.\n<#<Object:0x31836aea>>.respond_to?(:to_f) expected\n(Class: <Object>)"> expected but was
<"The arguments must respond to to_f; the first float did not.\n<#<Object:0xd8>>.respond_to?(:to_f) expected\n(Class: <Object>)">

Finished in 2.835 seconds.

172 tests, 980 assertions, 2 failures, 0 errors, 0 pendings, 1 omissions, 0 notifications
98.8304% passed


----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=28312&group_id=5650

From noreply at rubyforge.org  Fri Jun 25 03:24:55 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 25 Jun 2010 03:24:55 -0400 (EDT)
Subject: [test-unit-tracker] [ test-unit-Bugs-28312 ] test-unit's own tests
	fail on jruby
Message-ID: <20100625072455.4BF151858372@rubyforge.org>

Bugs item #28312, was opened at 2010-06-21 03:44
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=28312&group_id=5650

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Hans de Graaff (graaff)
Assigned to: Nobody (None)
Summary: test-unit's own tests fail on jruby

Initial Comment:
When trying to run the test-unit test suite on jruby I get the following test failures. The tests pass fine on ruby 1.8 and ruby enterprise edition.

  1) Failure:
test_assert_alias_method(Test::Unit::TC_Assertions)
    [/var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:19:in `check'
     /var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:55:in `check_assertions'
     /var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:82:in `check_fails'
     /var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:1146:in `test_assert_alias_method']:
Should have the correct message.
<"<#<Object:0x42bb0406>>.nonexistent doesn't exist\n(Class: <Object>)"> expected but was
<"<#<Object:0x30>>.nonexistent doesn't exist\n(Class: <Object>)">

  2) Omission: encoding test is for Ruby >= 1.9
test_assert_equal_with_different_encoding(Test::Unit::TC_Assertions)
/var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:319:in `test_assert_equal_with_different_encoding'

  3) Failure:
test_assert_in_delta(Test::Unit::TC_Assertions)
    [/var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:19:in `check'
     /var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:55:in `check_assertions'
     /var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:82:in `check_fails'
     /var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:842:in `test_assert_in_delta']:
Should have the correct message.
<"The arguments must respond to to_f; the first float did not.\n<#<Object:0x31836aea>>.respond_to?(:to_f) expected\n(Class: <Object>)"> expected but was
<"The arguments must respond to to_f; the first float did not.\n<#<Object:0xd8>>.respond_to?(:to_f) expected\n(Class: <Object>)">

Finished in 2.835 seconds.

172 tests, 980 assertions, 2 failures, 0 errors, 0 pendings, 1 omissions, 0 notifications
98.8304% passed


----------------------------------------------------------------------

>Comment By: Kouhei Sutou (kou)
Date: 2010-06-25 16:24

Message:
I've fixed them in trunk.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=28312&group_id=5650

From noreply at rubyforge.org  Fri Jun 25 03:25:05 2010
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 25 Jun 2010 03:25:05 -0400 (EDT)
Subject: [test-unit-tracker] [ test-unit-Bugs-28312 ] test-unit's own tests
	fail on jruby
Message-ID: <20100625072505.5A5B9185837A@rubyforge.org>

Bugs item #28312, was opened at 2010-06-21 03:44
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=28312&group_id=5650

Category: None
Group: None
>Status: Closed
Resolution: None
Priority: 3
Submitted By: Hans de Graaff (graaff)
Assigned to: Nobody (None)
Summary: test-unit's own tests fail on jruby

Initial Comment:
When trying to run the test-unit test suite on jruby I get the following test failures. The tests pass fine on ruby 1.8 and ruby enterprise edition.

  1) Failure:
test_assert_alias_method(Test::Unit::TC_Assertions)
    [/var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:19:in `check'
     /var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:55:in `check_assertions'
     /var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:82:in `check_fails'
     /var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:1146:in `test_assert_alias_method']:
Should have the correct message.
<"<#<Object:0x42bb0406>>.nonexistent doesn't exist\n(Class: <Object>)"> expected but was
<"<#<Object:0x30>>.nonexistent doesn't exist\n(Class: <Object>)">

  2) Omission: encoding test is for Ruby >= 1.9
test_assert_equal_with_different_encoding(Test::Unit::TC_Assertions)
/var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:319:in `test_assert_equal_with_different_encoding'

  3) Failure:
test_assert_in_delta(Test::Unit::TC_Assertions)
    [/var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:19:in `check'
     /var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:55:in `check_assertions'
     /var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:82:in `check_fails'
     /var/tmp/portage/dev-ruby/test-unit-2.0.9/work/jruby/test-unit-2.0.9/test/test_assertions.rb:842:in `test_assert_in_delta']:
Should have the correct message.
<"The arguments must respond to to_f; the first float did not.\n<#<Object:0x31836aea>>.respond_to?(:to_f) expected\n(Class: <Object>)"> expected but was
<"The arguments must respond to to_f; the first float did not.\n<#<Object:0xd8>>.respond_to?(:to_f) expected\n(Class: <Object>)">

Finished in 2.835 seconds.

172 tests, 980 assertions, 2 failures, 0 errors, 0 pendings, 1 omissions, 0 notifications
98.8304% passed


----------------------------------------------------------------------

Comment By: Kouhei Sutou (kou)
Date: 2010-06-25 16:24

Message:
I've fixed them in trunk.

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=28312&group_id=5650