search

keeganwitt / gmock

Automatically exported from code.google.com/p/gmock
6 stars 2 forks source link

testMockMatchMethodOfFinalJavaClassUsingIt is flacky #60

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I've experienced the testMockMatchMethodOfFinalJavaClassUsingIt to
sometimes fail using the maven clean test.

junit.framework.AssertionFailedError: expected:<yes> but was:<a value
matching the closure matcher>

Strange...

Original issue reported on code.google.com by julien.g...@gmail.com on 6 Feb 2009 at 9:30

GoogleCodeExporter commented 9 years ago 
which line?
158: assertEquals "yes", s.match { true }
or
162: this.assertEquals "yes", match { true }

Original comment by JohnnyJianHY on 6 Feb 2009 at 9:56

GoogleCodeExporter commented 9 years ago 
It's on line 162 for me. Did you manage to reproduced it or is it just me?

Original comment by julien.g...@gmail.com on 7 Feb 2009 at 9:14

GoogleCodeExporter commented 9 years ago 
Unfortunately, I cannot reproduce it. I think it depends on the execution order 
of tests.

Original comment by JohnnyJianHY on 7 Feb 2009 at 9:45

GoogleCodeExporter commented 9 years ago 
If it happens under Groovy 1.6, I won't be surprised as the new call site is 
introduced.

Original comment by JohnnyJianHY on 7 Feb 2009 at 11:47

GoogleCodeExporter commented 9 years ago 
Has it happened again?

Original comment by JohnnyJianHY on 16 Feb 2009 at 1:31

GoogleCodeExporter commented 9 years ago 
I've just run all tests 20 times in a row and couldn't reproduce it. I would
attribute it to a bug in my machine - or something we've fixed since...

Original comment by julien.g...@gmail.com on 16 Feb 2009 at 7:10