Details
-
Type:
Patch
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Component/s: seleniumhq-plugin
-
Labels:None
-
Similar Issues:
Description
Currently if any of the test cases fail the build is marked unstable. This patch changes it so that if any of the Selenium assert* methods, in any of the cases in the suite fail the build will be marked as a failure and if any of the Selenium verify* methods, in any of the cases in the suite fail the build will be marked as unstable.
This change better reflects the differences between an assertion (an unrecoverable error) vs a verification (something isn't quite right but the test can continue).
Code changed in hudson
User: : pascal_martin
Path:
trunk/hudson/plugins/seleniumhq/src/main/java/hudson/plugins/seleniumhq/SeleniumhqPublisher.java
trunk/hudson/plugins/seleniumhq/src/main/java/hudson/plugins/seleniumhq/SuiteResult.java
trunk/hudson/plugins/seleniumhq/src/main/java/hudson/plugins/seleniumhq/TestResult.java
trunk/hudson/plugins/seleniumhq/src/main/resources/hudson/plugins/seleniumhq/SeleniumhqPublisher/config.jelly
trunk/hudson/plugins/seleniumhq/src/main/resources/hudson/plugins/seleniumhq/SeleniumhqPublisher/config.properties
trunk/hudson/plugins/seleniumhq/src/main/resources/hudson/plugins/seleniumhq/SeleniumhqPublisher/config_fr.properties
trunk/hudson/plugins/seleniumhq/src/test/java/hudson/plugins/seleniumhq/SeleniumhqPublisherTest.java
trunk/hudson/plugins/seleniumhq/src/test/resources/hudson/plugins/seleniumhq/testResultWithFailureNoError.html
http://jenkins-ci.org/commit/32716
Log:
Add support for Use status of test commands instead of suites to determine UNSTABLE/FAILURE/SUCCESS
fix demand http://issues.jenkins-ci.org/browse/JENKINS-6837