Bug #8417

assert_in_epsilon(-1, -1) failed

Added by Nobuhiro IMAI 11 months ago. Updated 11 months ago.

[ruby-core:55035]
Status:Rejected
Priority:Normal
Assignee:Kouhei Sutou
Category:lib
Target version:-
ruby -v:ruby 2.1.0dev (2013-05-18 trunk 40801) [x86_64-linux] Backport:1.9.3: UNKNOWN, 2.0.0: UNKNOWN

Description

=begin
assertinepsilon(-1, -1) failed as below:

require "test/unit"

class AssertInEpsilonTest < Test::Unit::TestCase
def testplus
assert
in_epsilon(1, 1)
end

def testminus
assert
in_epsilon(-1, -1)
end
end

# >> Loaded suite -
# >> Started
# >> F
# >> ===============================================================================
# >> Failure:
# >> <-1> -/+ (<-1> * )[-0.001] expected to include
# >> <-1>.
# >>
# >> Relation:
# >> <<-1> < <-1>-(<-1>)[-0.999] <= <-1>+(<-1>)[-1.001]>
# >> testminus(AssertInEpsilonTest)
# >> -:9:in `test
minus'
# >> ===============================================================================
# >> .
# >>
# >> Finished in 0.01199642 seconds.
# >>
# >> 2 tests, 2 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
# >> 50% passed
# >>
# >> 166.72 tests/s, 166.72 assertions/s

Though I'm not sure the difference between "test" and "minitest",
minitest seems to be succeeded.

require "minitest/unit"

MiniTest::Unit::TestCase.new(?-).assertinepsilon(-1, -1)
=end

History

#1 Updated by Nobuhiro IMAI 11 months ago

=begin
Oops, I forgot to show the result.

require "minitest/unit"

MiniTest::Unit::TestCase.new(?-).assertinepsilon(-1, -1) # => true
=end

#2 Updated by Nobuyoshi Nakada 11 months ago

  • Status changed from Open to Feedback

I can't reproduce it.
And that failure message seems different.
What version of test/unit are you using?

#3 Updated by Kouhei Sutou 11 months ago

  • Status changed from Feedback to Rejected
  • Assignee set to Kouhei Sutou
  • % Done changed from 0 to 100

It is a test-unit gem bug.
I'll fix it in test-unit gem!

#4 Updated by Nobuhiro IMAI 11 months ago

Oh, I'm verry sorry, but I used test-unit external gem (2.5.4).
After removing it, the test-unit default gem (2.0.0.0) works fine.
Would you please to close this (or mark as 3rd patry's) issue? Thanks.

#5 Updated by Nobuhiro IMAI 11 months ago

It is a test-unit gem bug.
I'll fix it in test-unit gem!

I noticed that just now.. Thanks in advance!

Also available in: Atom PDF