|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
> Tests planned: 100, Tests run: 90, Tests passed: 90, Status: Unstable
> Tests planned: 100, Tests run: 110, Tests passed: 110, Status: Unstable
> Tests planned: 100, Tests run: 100, Tests passed: 100, Status: Stable
Tis indeed not so hard to do. However, should you have any failure, and the
job is configured to fail the build in case of failures, your build will
be marked as failure, instead of unstable.
On the other hand, if you planned 100 test cases, but only 90 were execute,
and the others were skipped, then with this new change your build will
be marked as unstable because the number of test cases doesn't match
the plan.
WDYT? Will release an alpha version to the alpha update site.