nunit

TwitterFacebook
Get flash to fully experience Pearltrees
http://blog.troyd.net/PermaLink,guid,21b4cfe8-9d82-443f-86a5-db2d93d6e617.aspx Instead of using a different Assert method for each different type of assertion (e.g.: Assert.AreEqual() for equality comparison, or Assert.IsTrue() for boolean evaluation), the new Constraint-Based Assert Model introduced in NUnit 2.4 utilizes only one Assert method named Assert.That() . This "one method" approach is possible due to the introduction of a set of what NUnit calls "syntax helpers" which are passed in as an argument to the method. You can also pass in "constraint objects", as they implement the IConstraint interface as well, however, this article will be focusing only on the "syntax helpers". Editoral Note: This new "one method" approach strikes me as an application of the GoF Strategy Pattern . The most common overloads to the Assert.That() method are as follows: Assert.That( object actual, IConstraint constraint ) Assert.That( object actual, IConstraint constraint, string message ) Assert.That( object actual, IConstraint constraint, string message, object[] parms )

Troy DeMonbreun - Learn the new NUnit 2.4 Constraint-Based Assert Model

HOW TO Unit Test BizTalk 2006 Orchestrations using BizUnit 2006 - The Code Project - Microsoft BizTalk Server

Introduction - Unit Testing Essentially a Unit Test is a procedure used to validate a particular piece of source code. Effective Unit Testing is vital to the success of any project. Unit Testing results in reduced defects in the next level of testing. Traditionally we have used NUnit to test any assembly ( *.DLL ). For testing BizTalk Orchestrations, we use a similar approach. http://www.codeproject.com/Articles/13926/How-to-Unit-Test-BizTalk-2006-Orchestrations-using

BizUnit Context Tutorial - The Code Project - Microsoft BizTalk Server

Introduction BizUnit is a very extensible testing framework. One of the core elements of BizUnit is the Context object. Unfortunately, the documentation does not explain how users can take advantage of it, and it is left to developers to try and understand it from some of the code snippets provided in the NDoc documentation. http://www.codeproject.com/Articles/16449/BizUnit-Context-Tutorial

MSBuild with NUnit

I’ve written about Unit Testing and Build Automation in the past, but mostly dealing with Java projects and tools (because I usually write about things I’m working on at the time). Well, I’ve started a .NET project for the first time in a while so I want to solve some of the samde problems in this environment. Why MSBuild? http://www.zorched.net/2006/11/28/msbuild-with-nunit/
http://bizunit.codeplex.com/

BizUnit - Automated Test Framework

The adoption of an automated testing strategy is fundamental in reducing the risk associated with software development projects, it is key to ensuring that you deliver high quality software. Often, the overhead associated with developing automated tests is seen as excessive and a reason to not adopt automated testing. BizUnit enables automated tests to be rapidly developed. BizUnit is a flexible and extensible declarative test framework targeted that rapidly enables the automated testing of distributed systems, for example it is widely used to test BizTalk solutions. BizUnit is fully extensible.
http://www.codeproject.com/Articles/13390/NHibernate-Best-Practices-with-ASP-NET-1-2nd-Ed

NHibernate Best Practices with ASP.NET, Generics, and Unit Tests - The Code Project - ASP.NET

Author's note added June 11, 2008 - Announcement of S#arp Architecture Thankfully, technologies evolve over the years. Accordingly, Microsoft has introduced ASP.NET MVC as an alternative to classic ASP.NET.
http://www.codeproject.com/Articles/3781/Test-Driven-Development-in-NET

Test-Driven Development in .NET - The Code Project - .NET

Although developers have been unit testing their code for years, it was typically performed after the code was designed and written. As a great number of developers can attest, writing tests after the fact is difficult to do and often gets omitted when time runs out. Test-driven development (TDD) attempts to resolve this problem and produce higher quality, well-tested code by putting the cart before the horse and writing the tests before we write the code.