[
https://issues.jboss.org/browse/ISPN-1906?page=com.atlassian.jira.plugin....
]
Sanne Grinovero commented on ISPN-1906:
---------------------------------------
Suggestion: I've noticed a similar problem previously, the cause was because of the
changed order of execution of tests.
We should of course not rely on execution order, but that's likely something has
slipped in. If needed there is @Test(dependsOnMethods) to force it,
or surefire has an option to define in which order it should execute test classes
(defaults to filesystem physical!! pretty much random across OS but consistent on several
runs on the same machine).
Sorry I might have written this somewhere else already, I thought I did on this issue.
Use recent test frameworks (TestNG + Surefire)
----------------------------------------------
Key: ISPN-1906
URL:
https://issues.jboss.org/browse/ISPN-1906
Project: Infinispan
Issue Type: Task
Components: Test Suite
Affects Versions: 5.1.2.FINAL
Reporter: Tristan Tarrant
Assignee: Galder Zamarreño
Fix For: 5.2.0.FINAL
The Infinispan test suite is a bit susceptible to the versions of the testing frameworks
we use. In particular upgrading the versions of TestNG and Surefire causes test failures
which otherwise wouldn't occur. Investigate why (most probably race conditions).t
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira