[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-686?pag...
]
Sanne Grinovero edited comment on HSEARCH-686 at 2/14/11 8:59 AM:
------------------------------------------------------------------
To reproduce: start org.hibernate.search.test.engine.NumericFieldTest. Should be fine. Now
change one of the asserted expectations, for example introduce: {code}assertEquals(3,
3);{code} and then change it into {code}assertEquals(3, 4);{code} Look at the resulting
exceptions :/
was (Author: sanne):
To reproduce: start org.hibernate.search.test.engine.NumericFieldTest. Should be fine.
Now change one of the asserted expectations, for example change: {code}assertEquals(3,
3);{code} into {code}assertEquals(3, 4);{code} Look at the resulting exceptions :/
Failing tests hide the assertion failure message by consequently
failing cleanup methods
----------------------------------------------------------------------------------------
Key: HSEARCH-686
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-686
Project: Hibernate Search
Issue Type: Bug
Reporter: Sanne Grinovero
Assignee: Hardy Ferentschik
Priority: Minor
Fix For: 3.4.0
It seems that if a Search test fails in the testmethod, the stacktrace and error messages
are hidden by cleanup methods which are invoked by parent test logic, which also fail as
the SessionFactory is closed and resources such as DirectoryProviders are already closed
so they fail to cleanup data and hide the true issue.
If a test does not fail, nothing wrong happens.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira