Not marking a build as failed with failing unit tests doesn't make any sense to me. We fail the build if a compile fails so why not with tests? What if I was working in a dynamic/interpreted language and so couldn't rely on compiler/type system to find what would be guaranteed run-time errors?
I'd prefer to use the MSTest plugin because the MSTest plugin performs the conversion from the .trx test output to the junit format that jenkins understands. -barrett On Thursday, September 6, 2012 1:51:00 PM UTC-4, Mark Waite wrote: > > You might consider the comments in this thread before you mark a job as > failed due to test failures: > > > http://jenkins.361315.n4.nabble.com/plugin-A-build-with-failed-tests-should-be-marked-as-Unstable-or-Failure-td3585663.html > > > If that guidance doesn't meet your needs and you decide that you still > want to fail the build on test failures rather than mark the build > "Unstable" on test failures, then I think the easiest way is to invoke > mstest.exe directly (instead of using the MSTest plugin to launch it) and > then have the MSTest batch file exit with a non zero exit code if any test > fails. > > Mark Waite > > > > ------------------------------ > *From:* bearrito <[email protected] <javascript:>> > *To:* [email protected] <javascript:> > *Sent:* Thursday, September 6, 2012 10:04 AM > *Subject:* MSTest Plugin doesn't fail the job on failing test. > > I would like the MSTest plugin to fail the job when a test fails. Is this > feasible ? > > > > > >
