Build status value
Karthik Krishnan (889●9●123●165)
| asked Oct 15 '14, 8:16 a.m.
edited Oct 17 '14, 10:37 a.m. by Jennifer Cianchetta-Riordan (251●2)
Is it possible to set "Unstable" (or equivalent to RTC terms) when only the "Tests" fail during the builds?
We don't want to set status failed for unit test failure Is this possible in RTC to set additional status apart from Success or Failure? |
One answer
Hi Karthik. The build status supports only OK, INFO, WARNING and ERROR values. However, it's possible to have error/failure test results not impact the overall build result when publishing them. e.g. the junitLogPublisher Ant task has a mayFailPattern= attribute, which can be set to the name of a test suite, or substring thereof. If matched, the tests are published as normal but any test error or failure will not impact the overall build result's status.
We use this in our own self-hosting, separating problematic / intermittently failing tests into "MayFail" test suites.
Comments Hi Nick,
1
How do you publish the test results currently? The Ant tasks for the 4 different unit test result formats we support all have the mayFailPattern attribute (but note that it's just a substring check, not actually pattern matching). The tasks are: junitLogPublisher, cppunitLogPublisher, mstestLogPublisher, and nunitLogPublisher. Right now we don't publish it yet but we wanted to use this. If we were to use junitLogPublisher could you please tell me how I could set these status?
For the test results publishing, see the doc on the Ant task and its mayFailPattern parameter:
If it's still not clear, let me know. Scripting to change the build status is possible, but shouldn't be necessary.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.