Wednesday, 25 June 2014

DUnit Integration with TeamCity

TeamCity supports number of testing frameworks out of the box. What about DUnit..?
Well, it is not supported out-of-the-box. When I searched around, one solution I found is to configure the test project to use the console runner and TeamCity would be happy. My CI server is now running like a charm. 





But wait, TeamCity should not have reported Success as there are failed tests I wrote intentionally. Let's take a look at the Build Log.




















Seems like TeamCity does not understand the language DUnit speaks. So we need to tell TeamCity to report the build status as failure when one of the test fails. 








Finally, it is red. Cool!


What's next? More fun with TeamCity and DUnit?

No comments:

Post a Comment