Hi Steinar, Thank you for this, no doubt you are right.
We now superstitiously continue with JUnit 3 naming conventions for test classes and test methods, whether we are using Junit3, 4 or TestNG (yes we use all three!) It was indeed when TestNG was introduced that we had this problem. For my taste I would not move away from a classic version, but I am not fashionable :) If you have not yet used Jenkins have a go: you will not look back. thanks Tim On 28 September 2012 16:08, Steinar Bang wrote: >>>>>> Tim Pizey : > >> Not everyone uses annotations, the surefire plugin requires the JUnit >> 3.8.1 naming conventions, > > That doesn't seem to be the case: > http://maven.apache.org/plugins/maven-surefire-plugin/examples/junit.html > > Quote: > "Surefire supports three different generations of JUnit: JUnit 3.8.x, > JUnit 4.x (serial provider) and JUnit 4.7 (junit-core provider with > parallel support)." > >> the Jenkins plugins assume the same conventions. > > Hm... I haven't yet tried Jenkins, but I would surprised if Jenkins does > anything outside of what maven would do, for a maven build...? > >> We have been bitten by People using JUnit4 and TestNG and hence >> skipping tests in Jenkins. > > I found this on Stack Overflow, someone who had surefire not picking up > tests marked with annotations: > > http://stackoverflow.com/questions/2021771/surefire-is-not-picking-up-junit-4-tests > > It seems that in this case, this was a case of TestNG requiring JUnit > 3.8.1 and shadowing a later dependance of JUnit 4. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Tim Pizey - http://pizey.net/~timp --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
