actually these were tests of code that the developers thought not to include threading or concurrency
I've been badly bitten by running the tests only once. they are unit tests, they should be fast enough to run them twice. and you should run them more than once and in a random order each time. now if it's integration tests... whole different storey. re your other point. I am consyantly amased at the java developers who think they don't have to know about threading... they all think that running the tests once with cobertura and having a successful run means that everything is fine... that is not best practice. maven is about being opinionated software. maven's opinion is that only by running the tests un instrumented can you prove the tests pass. if you don't like mavens opinion, you can have a hard time fighting it. stay on the naven way and run the damn tests twice - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 12 Jan 2011 17:39, "Hilco Wijbenga" <hilco.wijbe...@gmail.com> wrote:
