UnitTestEx v1.2 Released!

August 20, 2009 23:23 by garrymc

I’ve just released an update to the UnitTestEx component which as the following additions:

  • Re-factored API signatures to make them much simpler
  • ExecuteUnitTestScript to support in/out params
  • Renamed ExecuteUnitTestValidationScriptReader to ExecuteUnitTestScriptReader which also now supports in params
  • Added unit test for all database related features ie ExecuteUnitTestScript
  • Added database scripts to allow testing of the new unit tests.
  • Compare now supports the ability to treat empty collections as the same as null collections. This feature can be useful if de-serialize your expected results from an XML file and your actual forces some collections to be null but the default behaviour of the code is to have initialized collections.

For anyone who has been using an older version, this version represents a number of breaking changes. The changes however are not significant and the APIs are now quite stable.

If you haven’t checked out the component yet, take a look at the original post and the code on CodePlex.

Digg It!DZone It!StumbleUponTechnoratiRedditDel.icio.usNewsVineFurlBlinkList
kick it on DotNetKicks.com

Currently rated 3.1 by 24 people

  • Currently 3.083333/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Unit Testing and Test Spy Library Released!

May 20, 2009 21:12 by garrymc

Its been some time since my last post, so I thought I’d start back with news of a small Unit Testing library I’ve been using with my current client. I developed the library to solve a number of issues I was facing while doing my unit tests. The focus of the library is to provide support for:

  • Test Spy Pattern: a type of of fake that monitors calls and data passed rather than trying to mock the implementation. A discussion of the pattern can be found in the xUnit Patterns book.
  • Comparing entities: the amount of code generally required to test that an entities properties match those of the expected version can be large and tedious to write.
  • Data access testing: while using Fakes and the like is great, you still need to test the code that actually talks to the database. This usually ends up taking a reasonable amount of code to setup and execute, making the test harder to read.

This library provides solutions to the above problems which in my experience has produced cleaner tests that are easier to read and understand. The library comes with a fairly detailed User Guide so I wont go into the details of how everything works here, however I will provide a quick overview of how the library attempts to solve these issues.More... kick it on DotNetKicks.com

Currently rated 2.0 by 4 people

  • Currently 2/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5