From noreply at rubyforge.org Tue Oct 6 13:15:16 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue, 6 Oct 2009 13:15:16 -0400 (EDT)
Subject: [test-unit-tracker] [ test-unit-Feature Requests-27247 ]
assert_alias
Message-ID: <20091006171516.2D63C18582DE@rubyforge.org>
Feature Requests item #27247, was opened at 2009-10-06 10:15
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=21859&aid=27247&group_id=5650
Category: None
Group: None
Status: Open
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: assert_alias
Initial Comment:
Hi,
I sometimes create aliases for methods. I've found that in order to test aliases properly I resort to this code:
assert_true(Foo.instance_method(:original_method) == Foo.instance_method(:alias_method))
This is a handy way to smoke out synonyms vs aliases.
I'd like to be able to shrink that to this:
assert_alias(Foo, :original_method, :alias_method)
I suppose singleton aliases would either need a separate method or a 4th parameter.
What do you think?
Regards,
Dan
----------------------------------------------------------------------
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=21859&aid=27247&group_id=5650
From noreply at rubyforge.org Tue Oct 13 08:44:10 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Tue, 13 Oct 2009 08:44:10 -0400 (EDT)
Subject: [test-unit-tracker] [ test-unit-Feature Requests-27247 ]
assert_alias
Message-ID: <20091013124410.B6C831978285@rubyforge.org>
Feature Requests item #27247, was opened at 2009-10-07 02:15
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=21859&aid=27247&group_id=5650
Category: None
Group: None
Status: Open
Priority: 3
Submitted By: Daniel Berger (djberg96)
Assigned to: Nobody (None)
Summary: assert_alias
Initial Comment:
Hi,
I sometimes create aliases for methods. I've found that in order to test aliases properly I resort to this code:
assert_true(Foo.instance_method(:original_method) == Foo.instance_method(:alias_method))
This is a handy way to smoke out synonyms vs aliases.
I'd like to be able to shrink that to this:
assert_alias(Foo, :original_method, :alias_method)
I suppose singleton aliases would either need a separate method or a 4th parameter.
What do you think?
Regards,
Dan
----------------------------------------------------------------------
>Comment By: Kouhei Sutou (kou)
Date: 2009-10-13 21:44
Message:
Umm...
What about assert_equal_instance_method(:alias_method, :original_method, Foo)?
(expected value should be the first argument)
----------------------------------------------------------------------
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=21859&aid=27247&group_id=5650
From noreply at rubyforge.org Sun Oct 18 09:33:22 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 18 Oct 2009 09:33:22 -0400 (EDT)
Subject: [test-unit-tracker] [ test-unit-Bugs-27314 ] diff summary on test
failure does not handle fixnum comparisons appropriately
Message-ID: <20091018133322.BD9911858291@rubyforge.org>
Bugs item #27314, was opened at 2009-10-18 06:33
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27314&group_id=5650
Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Erik Hollensbe (erikh)
Assigned to: Nobody (None)
Summary: diff summary on test failure does not handle fixnum comparisons appropriately
Initial Comment:
call is assert_equal(nil, 1)
version is: 2.0.4
output is:
1) Failure:
test_03_convert(TestConverter) [./test/test_converter.rb:60]:
<0> expected but was
<1>
diff:
/opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/diff.rb:521:in `<': comparison of Fixnum with nil failed (ArgumentError)
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/diff.rb:521:in `_diff_lines'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/diff.rb:515:in `diff_lines'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/diff.rb:412:in `diff'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/diff.rb:409:in `each'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/diff.rb:409:in `diff'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/console/testrunner.rb:173:in `output_fault_message'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/console/testrunner.rb:125:in `output_fault'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/console/testrunner.rb:104:in `finished'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/fixture.rb:146:in `each_with_index'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/console/testrunner.rb:101:in `each'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/console/testrunner.rb:101:in `each_with_index'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/console/testrunner.rb:101:in `finished'
from /opt/ruby1.8/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `to_proc'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/util/observable.rb:78:in `call'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/util/observable.rb:78:in `notify_listeners'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/util/observable.rb:78:in `each'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/util/observable.rb:78:in `notify_listeners'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/testrunnermediator.rb:55:in `run_suite'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/console/testrunner.rb:81:in `start_mediator'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/console/testrunner.rb:51:in `start'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/testrunnerutilities.rb:24:in `run'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/autorunner.rb:310:in `run'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/autorunner.rb:52:in `run'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit.rb:320
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake/rake_test_loader.rb:5
----------------------------------------------------------------------
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27314&group_id=5650
From noreply at rubyforge.org Sun Oct 18 09:37:28 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 18 Oct 2009 09:37:28 -0400 (EDT)
Subject: [test-unit-tracker] [ test-unit-Bugs-27314 ] diff summary on test
failure does not handle fixnum comparisons appropriately
Message-ID: <20091018133728.EBB07158805C@rubyforge.org>
Bugs item #27314, was opened at 2009-10-18 06:33
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27314&group_id=5650
Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Erik Hollensbe (erikh)
Assigned to: Nobody (None)
Summary: diff summary on test failure does not handle fixnum comparisons appropriately
Initial Comment:
call is assert_equal(nil, 1)
version is: 2.0.4
output is:
1) Failure:
test_03_convert(TestConverter) [./test/test_converter.rb:60]:
<0> expected but was
<1>
diff:
/opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/diff.rb:521:in `<': comparison of Fixnum with nil failed (ArgumentError)
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/diff.rb:521:in `_diff_lines'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/diff.rb:515:in `diff_lines'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/diff.rb:412:in `diff'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/diff.rb:409:in `each'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/diff.rb:409:in `diff'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/console/testrunner.rb:173:in `output_fault_message'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/console/testrunner.rb:125:in `output_fault'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/console/testrunner.rb:104:in `finished'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/fixture.rb:146:in `each_with_index'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/console/testrunner.rb:101:in `each'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/console/testrunner.rb:101:in `each_with_index'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/console/testrunner.rb:101:in `finished'
from /opt/ruby1.8/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `to_proc'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/util/observable.rb:78:in `call'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/util/observable.rb:78:in `notify_listeners'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/util/observable.rb:78:in `each'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/util/observable.rb:78:in `notify_listeners'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/testrunnermediator.rb:55:in `run_suite'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/console/testrunner.rb:81:in `start_mediator'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/console/testrunner.rb:51:in `start'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/testrunnerutilities.rb:24:in `run'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/autorunner.rb:310:in `run'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/autorunner.rb:52:in `run'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit.rb:320
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake/rake_test_loader.rb:5
----------------------------------------------------------------------
>Comment By: Erik Hollensbe (erikh)
Date: 2009-10-18 06:37
Message:
Seems my initial assessment is wrong, assert_equal call has
the arguments of 0, 1... not sure what's going on here.
Sorry I can't be of more help.
----------------------------------------------------------------------
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27314&group_id=5650
From noreply at rubyforge.org Sun Oct 18 09:59:45 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Sun, 18 Oct 2009 09:59:45 -0400 (EDT)
Subject: [test-unit-tracker] [ test-unit-Bugs-27314 ] diff summary on test
failure does not handle fixnum comparisons appropriately
Message-ID: <20091018135945.A4B7E18582BC@rubyforge.org>
Bugs item #27314, was opened at 2009-10-18 22:33
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27314&group_id=5650
Category: None
Group: None
>Status: Closed
>Resolution: Accepted
Priority: 3
Submitted By: Erik Hollensbe (erikh)
Assigned to: Nobody (None)
Summary: diff summary on test failure does not handle fixnum comparisons appropriately
Initial Comment:
call is assert_equal(nil, 1)
version is: 2.0.4
output is:
1) Failure:
test_03_convert(TestConverter) [./test/test_converter.rb:60]:
<0> expected but was
<1>
diff:
/opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/diff.rb:521:in `<': comparison of Fixnum with nil failed (ArgumentError)
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/diff.rb:521:in `_diff_lines'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/diff.rb:515:in `diff_lines'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/diff.rb:412:in `diff'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/diff.rb:409:in `each'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/diff.rb:409:in `diff'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/console/testrunner.rb:173:in `output_fault_message'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/console/testrunner.rb:125:in `output_fault'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/console/testrunner.rb:104:in `finished'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/fixture.rb:146:in `each_with_index'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/console/testrunner.rb:101:in `each'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/console/testrunner.rb:101:in `each_with_index'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/console/testrunner.rb:101:in `finished'
from /opt/ruby1.8/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `to_proc'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/util/observable.rb:78:in `call'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/util/observable.rb:78:in `notify_listeners'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/util/observable.rb:78:in `each'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/util/observable.rb:78:in `notify_listeners'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/testrunnermediator.rb:55:in `run_suite'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/console/testrunner.rb:81:in `start_mediator'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/console/testrunner.rb:51:in `start'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/ui/testrunnerutilities.rb:24:in `run'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/autorunner.rb:310:in `run'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit/autorunner.rb:52:in `run'
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/test-unit-2.0.4/lib/test/unit.rb:320
from /opt/ruby1.8/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake/rake_test_loader.rb:5
----------------------------------------------------------------------
>Comment By: Kouhei Sutou (kou)
Date: 2009-10-18 22:59
Message:
Thanks for reporting.
I've fixed it in trunk.
I'll release new version soon.
----------------------------------------------------------------------
Comment By: Erik Hollensbe (erikh)
Date: 2009-10-18 22:37
Message:
Seems my initial assessment is wrong, assert_equal call has
the arguments of 0, 1... not sure what's going on here.
Sorry I can't be of more help.
----------------------------------------------------------------------
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27314&group_id=5650
From noreply at rubyforge.org Fri Oct 30 11:58:07 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 30 Oct 2009 11:58:07 -0400 (EDT)
Subject: [test-unit-tracker] [ test-unit-Bugs-27374 ] omit_if unexpected
behavior
Message-ID: <20091030155807.B18D41858283@rubyforge.org>
Bugs item #27374, was opened at 2009-10-30 15:58
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27374&group_id=5650
Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: David MARCHALAND (marchaland)
Assigned to: Nobody (None)
Summary: omit_if unexpected behavior
Initial Comment:
Hi,
Based on my understanding, what I expect with the omit_if(cond, &block) method is the following behavior:
if cond
omit(&block)
else
&block
end
In Test::Unit 2.0.5, implementation is the following:
omit(&block) if cond
Hence, "&block" will never be executed...
What's your opinion?
Regards,
David
----------------------------------------------------------------------
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27374&group_id=5650
From noreply at rubyforge.org Fri Oct 30 19:08:20 2009
From: noreply at rubyforge.org (noreply at rubyforge.org)
Date: Fri, 30 Oct 2009 19:08:20 -0400 (EDT)
Subject: [test-unit-tracker] [ test-unit-Bugs-27374 ] omit_if unexpected
behavior
Message-ID: <20091030230820.BF85E1858289@rubyforge.org>
Bugs item #27374, was opened at 2009-10-30 15:58
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27374&group_id=5650
Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: David MARCHALAND (marchaland)
Assigned to: Nobody (None)
Summary: omit_if unexpected behavior
Initial Comment:
Hi,
Based on my understanding, what I expect with the omit_if(cond, &block) method is the following behavior:
if cond
omit(&block)
else
&block
end
In Test::Unit 2.0.5, implementation is the following:
omit(&block) if cond
Hence, "&block" will never be executed...
What's your opinion?
Regards,
David
----------------------------------------------------------------------
>Comment By: David MARCHALAND (marchaland)
Date: 2009-10-30 23:08
Message:
Same trouble with omit_unless method, unexpected behavior.
Regards,
David
----------------------------------------------------------------------
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=21856&aid=27374&group_id=5650