Circles and Crosses » TDD http://ox.no Håvard Stranden's website Sat, 20 Aug 2011 00:11:11 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 Problems running .NET 4.0 tests using NUnit 2.5 with (or without) Continuous Testing? http://ox.no/posts/problems-running-net-4-0-tests-using-nunit-2-5-with-or-without-continuous-testing http://ox.no/posts/problems-running-net-4-0-tests-using-nunit-2-5-with-or-without-continuous-testing#comments Wed, 11 Aug 2010 09:11:08 +0000 Håvard http://ox.no/?p=222 Continue reading →]]> NUnit 2.5 up to and including 2.5.4 fails to properly detect certain revisions of .NET 4.0, causing it to crash. The issue is documented in this bug report on LaunchPad. The bug has been fixed in 2.5.5 and later, so go grab the latest version of NUnit 2.5 and run your tests smoothly again, preferably on each build using Continuous Testing, of course. :)

]]> http://ox.no/posts/problems-running-net-4-0-tests-using-nunit-2-5-with-or-without-continuous-testing/feed 0 Continuous Testing for Visual Studio http://ox.no/posts/continuous-testing-for-visual-studio http://ox.no/posts/continuous-testing-for-visual-studio#comments Sat, 08 May 2010 00:36:27 +0000 Håvard http://ox.no/?p=161 Continue reading →]]> The other night is was playing around with a side project. I try to use a rather strict TDD approach for these projects, and so I run my tests a lot of times as I move forward, and spend quite some time waiting for the result before I move forward. This is a tedious and frankly unnecessary manual step; what I needed was continuous testing – unit tests that test themselves continuously, making sure I don’t break anything.

I remembered reading about JUnit Max by Kent Beck, a continuous testing plugin for Eclipse, that runs your unit tests in the background and unobtrusively tells you when a test fails, allowing you to do what you do best: write code. JUnit Max seems like a great thing, and now I needed the same thing for Visual Studio. A quick Google didn’t yield any add-ins, extensions or packages, so I decided to create one.

The result is Continuous Testing for Visual Studio, a small extension which runs your unit tests each time you build your solution, and reports failing tests to the error list so you can navigate to the line that failed and make the test pass. The extension significantly improves my workflow by removing a tedious manual step of running unit tests, so I encourage you to take it for a spin. Continuous Testing can be downloaded for Visual Studio 2008 and Visual Studio 2010. Future updates and versions will be announced on the Continuous Testing home page.

UPDATE Jun 17th, 2010: I’ve receive a lot of feedback through various solutions online. To be able to help you and/or improve Continuous Testing for Visual Studio, I need samples from you that reproduce the problems you are experiencing. Do not hesitate to leave a comment here, and provide your e-mail address when commenting, and you will receive a reply.

]]> http://ox.no/posts/continuous-testing-for-visual-studio/feed 27