testingReflections.com - NUnit

NUnit Test Runner and Profiler for Visual Studio

Thu, 05 Jan 2006 08:35:11 -0600

[textile]Looks interesting... Will have to investigate this tool...

"MailFrame NUnit TestRunner":http://www.mailframe.net/Products/TestRunner/2005/

I like the look of the visual integration with the Visual Studio editor...

Model View Presenter - is testing the presenter enough?

Mon, 28 Nov 2005 02:11:07 -0600

Source code: Download

Lately, I have noticed that the Humble Dialog Box or Model View Presenter are gaining more and more acceptance among software developers, especially in agile communities, because of its benefits regarding the very good separation between the view and the behavior and because it can be very easily unit tested, on a problematic field: user interface.

Testing your web UI using SWExplorerAutomation and NUnit

Thu, 01 Sep 2005 20:13:42 -0500

[textile]In my "previous posts about SWExplorerAutomation (SWEA)":http://www.testingreflections.com/node/view/2592, I addressed a couple of initial problems with getting "SWEA":http://home.comcast.net/~furmana/SWIEAutomation.htm to work on a specific configuration of machine.

Having got past that, I moved on to more interesting things... Specifically, using SWEA under NUnit.

I won't go into the detail of any of the SWEA main features since "Alex Furman":http://www.alexfurman.net does that better than me in his "Flash Demo":http://home.comcast.net/~furmana/SWExplorerAutomation.html and developer documentation available on the "SWEA home page":http://home.comcast.net/~furmana/SWIEAutomation.htm

When should you use SWEA? Well, there are so many different circumstances where it would be appropriate and many where it wouldn't... rather than guess your circumstances, I'll tell you about mine:

NUnitASP Architecture walkthrough video from Jim Shore

Sun, 21 Aug 2005 04:31:48 -0500

Jim Shore, one of the Agile folks out there, has created a nice animated video using Camtasia that talks about how the NUnitASP Architecture works. It's not really for those without any NUnitASP experience but it's definitely interesting and I hope there will be more of this to come. Here's the full excerpt from his email to the Test-First user interfaces mailing list at Yahoo: At the Agile 2005 conference, Joshua Kerievsky talked about using alternatives to hands-on coaching to "commoditize" training in XP. I found it to be a thought-provoking talk. Well, tI've tried out one of Joshua's ideas and I'm very pleased with the result. NUnitAsp is a tool for test-driven development of ASP.NET. I've produced a video that talks about NUnitAsp's architecture, the challenges that you face in NUnitAsp, and ways to overcome them. It's a neat presentation, very compact at eight minutes, and well illustrated with animation and figures, if I do say so myself. Although it's intended for advanced users, I think anybody interested in NUnitAsp or TDD in general will learn something from watching it. I'm very happy with the way this turned out and I hope you'll take a look. Please let me know what you think. You can find the video on the NUnitAsp web site: http://nunitasp.sf.net/AdvancedNUnitAsp.html This is the first time I've produced a video like this and I've blogged about the experience here: http://www.jamesshore.com/Blog/Advanced-NUnitAsp-Video.html Enjoy!

NUnit Converter: switch from NUnit to VSTS

Mon, 04 Jul 2005 00:49:21 -0500

A tool from Jim Newkirk that converts NUnit Test Code into tests compatible with Visual Studio 2005 Team System.

NUnit in Hebrew?

Thu, 24 Mar 2005 00:59:06 -0600

This is a question to all the Hebrew-speaking readers of this blog (all 3 of you): One of the upcoming features on NUnit will be a localization kit which will enable it to be run in different language contexts. So:

Would you want to use a version if NUnit in Hebrew? explain why (yes or no)
Would you want to he

Test Driven Development Using NUnit in C#

Sat, 29 Jan 2005 03:44:37 -0600

When sitting down to create an application, many developers start by writing the code. Test Driven Development emphasizes the opposite, stressing the need to prepare test scenarios or test cases before writing the code itself. This seemingly backwards approach has some benefits. First of all, it requires that the programmer be very clear about what tests the program should pass and what test it should fail, bringing such concerns to the forefront of the software design process. Furthermore, by meticulously detailing what tests a system should pass and fail we can use tools to automate most of our tests. An automated job is one that's always very, very easy to do. These automated tests are meant to be run every time there's a code change and are referred to as unit tests.

SharpDevelop develops NUnit integration

Sat, 29 Jan 2005 03:57:23 -0600

Oh this is cool. SharpDevelop, the open source .NET editor, has built in NUnit integration. I'm still not sure what that really means, but I intend to find out. Hopefully it will be just like the JUnit integration found in similar Java projects.

NUnit extended: Beyond Assert

Tue, 11 Jan 2005 00:25:16 -0600

NUnit provides a basic set of assertions in the Assert class. We can compare two objects for equality or identity, test a boolean expression for truth or falsehood or check whether an object is null. Building on these assertions, it's possible to develop more complex tests.But that doesn't mean it's easy! Using these simple building blocks means that the developer must provide all the code to make the checks as well as building a meaningful error message in case of failure.

Testing Code-Generated Code with NUnit, Temporary Files, Voodoo, Rubber Bands and Reflection

Thu, 06 Jan 2005 00:46:29 -0600

We're into Unit Testing here and getting more so every day. We also do a lot of code generation as well, and struggled with how to test that the code generation works from end to end. [..] These [generated] objects should compile, have the correct attributes, be create-able at runtime, and serialize correctly.Here's how we run CodeSmith in the NUnit tests to generate into temporary .g.cs files. The ".g.cs" extension is our own invention, allowing us to keep track of what's generated and what's written by hand.

Unit-testing with multiple cultures in MbUnit and NUnit

Sun, 12 Dec 2004 02:55:57 -0600

It's a good idea, when unit-testing your classes, to test under multiple circumstances -- such as multiple cultures. Sure, a routine may work great when run under a given culture, say US English, but what if it is run on a Spanish or Japanese machine?MbUnit makes it easy to run tests under different cultures. If NUnit is your tool of choice, you need to do a little bit more work.

James Newkirk blogs again

Wed, 08 Dec 2004 00:38:49 -0600

James Newkirk breaks his blogging silence with two good posts. The first one continues the Bookmark Collection example Test Driven Development series. The other explains why he makes test fixture member variables static (and why it’s a good practice).

Unit testing with Cassini and NUnitASP: A complete example

Mon, 06 Dec 2004 00:05:19 -0600

A complete example of how you can use Cassini in combination with NUnitASP to unit test ASP.NET web pages without IIS. Uses Scott Hanselmans original code with some minor changes.Author: Anders NoråsPublished: December 2, 2004

NUnit Unit Testing of ASP.NET Pages, Base Classes, Controls and other widgetry using Cassini

Mon, 06 Dec 2004 00:06:25 -0600

There's a lot of info out there on how to cobble together NUnit Unit Testing of ASP.NET Pages and assorted goo. NUnitASP is a nice class library to facilitate this kind of testing, but it doesn't solve a few problems:- Do you have/want a Web Server on your Test/Build machine?- How do you get your Test Pages and such over to the Web Server? Just automatically copy them?- Are your Test cases self-contained? That is, do they require external files and other stuff to be carried along with them?

Extending NUnit easily with version 2.2.1 (finally!)

Mon, 06 Dec 2004 00:11:14 -0600

I finally got some time so I sat down with the latest version of NUnit - 2.2.1 and tried using its extensibility features like the ability to create new custom test attributes that change test behavior, hopefully ridding myself of more complex projects that I had to do in the past (such as using interception or create a whole new binary version of Nunit just so that this could be done) . I'm glad to say that it worked out great! NUnit 2.2.1 finally allows one to (no so)easily add custom attributes such as Rollback to NUnit without resorting to violence. Yey! Unfortunately, the process is still too bureaucratic (for me at least), requiring the developer to add 3 new classes for each test attribute. I took it upon myself to check and see if this process could be made easier and it does :) I basically created a base class you inherit from and does all the nasty work for you. Here's how easy it is to create a new attribute that does tracing on your unit tests:

[AttributeUsage(AttributeTargets.Method, AllowMultiple=false)]