Handling flaky GUI tests correctly in a Jenkins-Junit-mvn-Selenium setup.

Same tests but two different stories (from mvn and junit)

A wise man, once said, “Tests should be trustworthy, quick and should run at the right time. If not, there is little value in them”

<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>3.0.0-M5</version>
<configuration>
<rerunFailingTestsCount>2</rerunFailingTestsCount>
<skipAfterFailureCount>10</skipAfterFailureCount>
</configuration>
</plugin>
For total 31 tests, where mvn gives the correct numbers. Junit parsed results are giving false negatives and a false total count.

A learner, creator and mixed automation artist.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store