[
https://jira.codehaus.org/browse/MRM-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=302409#comment-302409
]
Eric Barboni commented on MRM-1638:
-----------------------------------
Sorry I had this parameter to run several time to check for reproductability
and give more error because 1 run can be successful with luck.
My point is to use the jdk7 job to stress test junit and help making them more
reliable according to the jdk7 implementation change.
Example of a potential test:
testAdd and testRemove on a same list
Add is adding one element , remove is removing one element
Theoricaly:
testRemove may be executable alone, in this dummy example it fail (deleting
from empty)
or several time not
Thats why I introduce a loop in the 1.7 testrunner. My evil plan was to set the
loop to more than 2 :p but I don't want to destroy jenkins.
> Improve unit test for archiva build
> -----------------------------------
>
> Key: MRM-1638
> URL: https://jira.codehaus.org/browse/MRM-1638
> Project: Archiva
> Issue Type: Task
> Components: Build
> Affects Versions: 1.4
> Environment: jdk 7.
> Reporter: Eric Barboni
> Assignee: Olivier Lamy
> Fix For: 1.4-M3
>
> Attachments: dummyRunner.patch, surefirereport.txt,
> unitRunnerallbuild.patch
>
>
> Due to change in jdk implementation in jdk7 test methods are executed in
> random order.
> As some unit test in archiva depend on certain order they fail random.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
