DUnit test fail doesn't fail build

Continua CI Discussion
1

Hello,

Firstly, I'm really liking Continua! We're trialling FinalBuilder at the same time and they are working great together! I've run into some problems with DUnit actions however, which I'm hoping is just a misunderstanding on my part.

I have a build whose job it is to do nothing but monitor our repo for changes, and then build and run unit tests. There are multiple DUnit test actions in the build stage. This appears to be working for the most part, however:

  1. The build correctly reports the number of unit tests run, however it shows them all as passing when in fact some are failing (the log output confirms some are failing)
  2. 'Save report as artifact' doesn't seem to be working? At least I cannot find the report xml file and it is not showing up on the artifacts tab of the build
  3. The 'Unit Tests' tab, shows no tests, but build overview shows tests run. 

All our tests are using the DUnit XML runner here: https://github.com/VSoftTechnologies/DUnit-XML. Running the tests outside of continua I can confirm that the XML output does show some tests as failing:

My DUnit action looks like this:

dunit-setup.jpg

Some XML samples from the XML report:

  
    Bad current period., expected: <41105> but was: <41106>








And the build result:

001_dunit-overview.jpg

And for completeness, log output from one of the DUnit actions with a failing test:

dunit-log.jpg

2

Hi Joel

Thanks for the feedback. It seems someone here rewrote the NUnit xml report parser and made it a bit more strict on the structure of the report file, which then broke the DUnit Action. I have pushed an updated DUnit xml runner to github, however it will only work with the next Continua build as I had to make some other minor changes to the parser. I have a build running at the moment, I’ll post on this forum later tonight with the build info.

3

Thanks Vincent, build 889 is failing the DUnit tests where expected. Much appreciated!

4

Excellent, thanks for testing.