Github user cardil commented on the issue:
https://github.com/apache/maven-surefire/pull/112
Is there something to fix with this PR or everything is okey now?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user cardil commented on the issue:
https://github.com/apache/maven-surefire/pull/112
:palm_tree: anyone there?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user cardil commented on the pull request:
https://github.com/apache/maven-surefire/pull/112#issuecomment-210342842
@Tibor17 Yes. Actually, I started development in that way. For example:
`-DrunOrder=random:123456`. But, that lead to some dirty code because
`RunOrder` is a
GitHub user cardil opened a pull request:
https://github.com/apache/maven-surefire/pull/112
Adding support for externally passed random seed and printing used seed on
console
It's good practice to execute tests in random order. That ensures tests are
atomic and not depend on