Thursday, May 29, 2008

Announcing Gallio Alpha 3 Update 2

Today we are releasing an update to Gallio Alpha 3 with a few new features.

Download here: (link)

New and Noteworthy

ReSharper v4.0 Beta Integration

If you haven't already heard, ReSharper v4.0 Beta is out!  (link)

And now we have support for it...

Gallio Test Report Action in ReSharper

ReSharper's unit test explorer is a great tool but it does not currently support all of the features needed for full native integration with Gallio.

For example, there is no way for us to display embedded images -- such as screenshots -- as part of the test output.  There are also some limitations as to how we can present the results of data-driven tests -- like Row-based tests -- in ReSharper.

No matter.  We have now added a custom action to display the full Gallio Test Report.


We have also made a few other small improvements to the output.

Unfortunately stack traces still are not clickable and there does not seem to be much we can do about it just now due to ReSharper limitations.

Pex Integration for MbUnit

Microsoft Pex has finally be released!  (link)

We already had support for an earlier prerelease version of Pex but we have now upgraded it to the latest edition.

The basic idea is that you can write parameterized tests using MbUnit v3 syntax and run Pex against them to generate test cases.

Step 1: Add a reference to MbUnit.Pex.


Step 2: Add the MbUnit Pex package attribute to your test assembly.


Step 3: Give Pex something to chew on.


Step 4: Pex It!


Step 5: Examine the generated tests.


There you go!

MbUnit v3 Contract Verifiers

I've added a couple of test fixtures to help verify common contracts such as equality and correct exception implementation.

Currently you use these verifiers by creating subclasses.  However, I'm tempted to transform the verifiers into mixins in the long run.


This checks Equals, GetHashCode(), IEquatable<T>.Equals(), operator== and operator!=.  You just need to provide the verifier with suitable distinct instances of your type.



This checks that an exception is serializable and has the standard constructors.


Upcoming Stuff

There's a bunch of new stuff on the way in Alpha 4 as we march onwards to feature-completeness.

Here's a little list to whet your appetite:

  • First partial draft of the Gallio Book.
  • Constraints framework.
  • Improved assertions.
  • .Net 3.5 features.
  • Workspace model for managing test project resources like historical test reports.
  • Metadata in CSV files.
  • [Factory] attribute for easier implementation of custom data sources.
  • New plug-in model and performance optimizations (might slip to Alpha 5).

I'm aware that there are a number of pending bugs and feature requests for the standard Gallio GUI (Icarus).  If you're interested in giving Graham a hand with this please let me know!

Ditto for the Visual Studio Team System integration.

Technorati Tags: ,

Tuesday, May 27, 2008

Help wanted: Release and Promotion Manager for Gallio and MbUnit

I'm looking for a volunteer to help release and promote new editions of Gallio and MbUnit.

If this sounds like something that would interest you, please let me know.


Release and Promotion Manager


  • Draft the release criteria.
  • Ensure the release criteria have been met.
  • Publish the release notes and release files.
  • Keep the website updated with news and useful resources.
  • Promote Gallio and MbUnit online and in the local community.
  • Produce articles, tutorials, podcasts, and other educational or promotional materials.
  • Monitor reactions from users and use it to steer subsequent releases.

Salary:  Cookies, chocolate, beer or other treat of your choice.

Technorati Tags: ,

Monday, May 19, 2008

MSBuild v3.5 ToolsVersion Attribute Gotchas

I just spent an hour debugging a project trying to use the new Properties and AdditionalProperties metadata in MSBuild v3.5.  (MSDN)

This special metadata is used to pass properties to MSBuild projects that are invoked using the MSBuild task.



<Project DefaultTargets="Test" xmlns="" ToolsVersion="3.5">
    <Project Include="b.proj">

  <Target Name="Test">
    <MSBuild Projects="@(Project)" />


<Project DefaultTargets="Test" xmlns="" ToolsVersion="3.5">
  <Target Name="Test">
    <Message Importance="High" Text="Foo=$(Foo)" />

Then when you run %SystemRoot%\Microsoft.NET\Framework\v3.5\MSBuild.exe a.proj, it should print out: Foo=123.  Woot!

We have successfully passed some properties to a recursive invocation of MSBuild.

ToolsVersion is Essential

Now what happens if you omit ToolsVersion="3.5".

Well, it you omit it from b.proj then the script will still work.

But it you omit it from a.proj MSBuild will run in a v2.0 compatibility mode.  So the value of the Foo property will NOT be passed into b.proj.  Not too surprising but it took me a little while to track it down.

This just goes to show how important the ToolsVersion attribute is.  Be careful!

Friday, May 16, 2008

Announcing Gallio v3.0 Alpha 3 Update 1

In my previous post, I mentioned that MbUnit v3's TestFixture attribute is now optional.  I have also fixed a couple of minor bugs.

Download Alpha 3 Update 1: GallioBundle-

Technorati Tags: ,

Thursday, May 15, 2008

MbUnit TestFixture Attribute is Now Optional

Historically, MbUnit has used a custom attribute called TestFixture to indicate that a class contains tests.

This isn't the only such attribute.  Other custom attributes, such as AssemblyFixture in MbUnit v3, denote various special kinds of fixtures.  However, TestFixture is the standard and most frequently used kind of fixture.

When James Newkirk and Brad Wilson designed xUnit.Net they omitted several features that they felt were redundant, confusing, or harmful.  TestFixture, long a staple of unit testing frameworks in .Net was one such piece of syntax that was axed: it was simply redundant.  A class is obviously a test fixture if it is not abstract and it contains suitably annotated test methods.

In a previous post I asked whether people felt that MbUnit should follow suit with xUnit.Net and either drop TestFixture altogether or make it optional.  The general sentiment seems to have fallen in the latter category.

So effective now, in MbUnit v3, TestFixture is optional.  I will publish an update to Gallio Alpha 3 with this enhancement shortly.


1. Simple fixture in C#.

public class SimpleFixture
    public void SimpleTest()
        Assert.AreEqual(4, 2 + 2);

2. Simple fixture in F#.

using MbUnit.Framework

let SimpleTest() = Assert.AreEqual(4, 2 + 2)

3. Data-driven fixture in C# using generic type parameters.

[Row(typeof(List<int>), typeof(int))]
[Row(typeof(Dictionary<string, int>), typeof(KeyValuePair<string, int>))]
public class DataDrivenFixture<T, S> where T : ICollection<S>, new()
    public void CountIsIncrementedWhenOneItemIsAdded()
        T collection = new T();
        Assert.AreEqual(1, collection.Count);

4. A different data-driven fixture in C# using a constructor.

public class HomestarRunnerProductTest
    private string productName;
    private Product product;

    [Row("Fluffy Puff Marshmallows")]
    [Row("Cheat Command O's")]
    public Fixture(string productName)
        this.productName= productName;

    public void BuyProduct()
        product = Store.BuyProduct(productName);

    public void ReturnProduct()

    public void ShouldComeInAShinyBox()

    public void ShouldTasteSweet()
        Assert.AreEqual(Flavor.Sweet, product.Flavor);

5. Another data-driven fixture in C# using fields.

public class DataDrivenFixture
    [Column(OS.Windows, OS.Mac, OS.Linux)]
    public OS os;

    [Column(100, 1000, 10000)]
    public int dataSetSize;

    public void TestConfiguration()
        // ... do something with os and dataSetSize

6. A fixture represented as a static class with static test methods in C#.

public static class StatelessFixture
    public static void StatelessTest()
        Assert.AreEqual(4, 2+ 2);

7. A data-driven fixture in F# using a constructor.  (hypothetical)

I was going to demo something similar using F# but I couldn't get it to compile an attribute with object[] parameters.

I tried a bunch of variations but the only thing I could get to compile properly was a Row with an empty array.  Other attempts variously spit out errors like "error FS0191: invalid custom attribute value (not a constant): Format`5.ctor.1@[obj, obj, obj, obj, unit]`"2". "

Looks like there are bugs in the F# compiler as it does not seem to support array creation or type expressions as valid attribute values.

using MbUnit.Framework

[<Row( [| 123, "123" |] )>]             <--- does not compile in F# 1.9.4.
type when_string_formatter_receives_an_integer = { value : int, formattedResult : string } with
    member f.it_should_format_the_value_as_a_string() = Assert.AreEqual(f.formattedResult, StringFormatter.Format(f.value));

Final Remarks

The above examples only just scratch the surface of the supported variations.  Really, you can pick and choose the style you wish to use in your tests as you like.

P.S. I also fixed the bug that prevented Jim Burger from using MbUnit effectively with F#.  (more details)

Technorati Tags: ,

Tuesday, May 13, 2008

Announcing Gallio v3.0 Alpha 3

Today we have released Gallio v3.0 Alpha 3, including a preview of MbUnit v3.  Gallio Leaf

The installer is available here: GallioBundle- (temporary link)

It will also be available from the Gallio website shortly:

There has been quite a lot of progress in this release including new features, bug fixes, and various internal changes to make it easier for runner and framework authors to build new cool stuff on top of Gallio.

Here is a quick summary of these changes.

New and Notable

New Features

1. Annotations

Annotations are a means for test frameworks to communicate errors, warnings and informational messages to the user in association with particular code elements.

MbUnit v3 uses annotations to inform the user about improperly used attributes and to highlight points of interest such as ignored or pending tests.

Annotations are displayed as messages in test reports.


They manifest as error/warning stripes in R#.


Graham Hay has also added an Annotation view in the Icarus GUI.  Double-clicking on the annotation displays the source code.


2. Report Enhancements

HTML reports now include navigation stripes to provide a quick overview of the contents of the report and to navigate to failed, inconclusive and skipped tests.

When JavaScript is enabled, test results are automatically collapsed for ease of reading.  They are automatically expanded during navigation.


HTML reports can grow to become quite large when there are many tests.  Accordingly, we have added a "Condensed" version of this report that omits passing tests.  This is particularly useful in combination with CruiseControl.Net.


3. Icarus Test Execution Log

Graham Hay has added a new Execution Log view to Icarus.  You can view test results here while tests execute.   If you periodically refresh the view then you can watch test execution in near real-time including output from long-running tests that are still in flight.


4. Test Assembly Configuration Files

Gallio now provides all of the machinery required to support test assembly configuration files.  All frameworks and adapters can benefit from this support, including MbUnit v3.  Just create a configuration file named: "MyTestAssembly.dll.config" and put it next to your test assembly (assuming it is called MyTestAssembly).

5. MSTest Adapter

Julian Hidalgo implemented an adapter for MSTest.  This feature enables all Gallio runners to run MSTest tests.  One of the interesting consequences of this design is that R# v3.1 is now capable of viewing and running MSTest tests via Gallio.


6. Visual Studio Team System Integration (Experimental)

Gallio now includes an experimental ITip provider for integration with Visual Studio Team System 2008.

To use it, be sure to select the feature in the Gallio Installer.  It is currently excluded from installation by default because of its experimental nature.

Then just load up your favorite test project in Visual Studio 2008 and run a Build.  The tests should now appear in the Visual Studio Test View.  You can then run them from there.  It should work with all supported test frameworks.


As far as I know, we are the first Open Source testing project to provide this kind of integration.

If would like to contribute to the development of this feature please let me know!

7. Test Runner Extensions

Many new features can be added to Gallio by implementing plug-ins.  However, some users have requested the ability to extend test runners to change how test results are reported.

Gallio Alpha 2 included an ITestMonitor interface that roughly served this purposes by making it possible to inject additional behavior into the test runner's event handlers.  In Gallio Alpha 3, we have introduced the ITestRunnerExtension interface and provided a mechanism for loading extensions into the runners by means of an additional argument.

Implementing a test runner extension is straightforward:

  1. Create a new assembly for your extension.
  2. Add a reference to Gallio.dll.
  3. Create a subclass of TestRunnerExtension.
  4. In the Initialize method, register event handlers on the Events object provided to the extension.
  5. Build your assembly.
  6. Copy the file wherever you like.

Using a test runner extension is similar to registering an MSBuild logger.

  • If you are using Gallio.Echo.exe (the command-line test runner), add an argument like: "/extension:MyFancyExtension,MyFancyExtension.dll".
  • If you are using the Gallio NAnt or MSBuild tasks, the process is similar.  Refer to the documentation of these tasks for details.
  • There is a built-in extension for debugging.  Add "/extension:DebugExtension,Gallio" or an equivalent argument to enable it.  Be sure to also set the message verbosity to Debug.

The plan is to open up more of the platform to lightweight extensions of this sort.

8. Parameterized Test Enhancements

MbUnit v3 now fully supports generic test fixtures and test methods and various other parameterizations.

A test can now be parameterized in any of the following ways:

  • Adding a method parameter to a test method.
  • Adding a generic method parameter to a test method.
  • Adding a constructor parameter to a test fixture.
  • Adding a field to a test fixture.
  • Adding a writable property to a test fixture.
  • Adding a generic type parameter to a test fixture.

Correspondingly data-source attributes can be specified on any of the following code elements:

  • Test methods.
  • Test method parameters.
  • Test method generic parameters.
  • Test fixture types.
  • Test fixture constructors.
  • Test fixture constructor parameters.
  • Test fixture fields.
  • Test fixture properties.
  • Test fixture generic parameters.

So there are many choices, but each choice is quite simple.

Here are a few interesting combinations.

A basic "Row"-test.

Note: The [RowTest] attribute is not needed anymore and has been eliminated.

public class Fixture
    [Row(3, 4, 5, true)]
    [Row(1, 2, 3, false)]
    public void Test(int a, int b, int c, bool expectedResult)
        Assert.AreEqual(expectedResult, Math.IsPythagoreanTriple(a, b, c));

A generic "Type"-test.

Note: The [TypeFixture] attribute is not needed anymore and has been eliminated.

public class Fixture<T> where T : IList<int>, new()
    public void Test()
        T list = new T();
        Assert.AreEqual(1, list.Count);

A combinatorial test.

Note: The [CombinatorialTest] attribute is not needed anymore and has been eliminated.

public void Test([Column(0, 1)] int a, [Column("a", "b")] string b, [Column(false, true)] bool c)
    // Test something with the specified combination.
    // Will be executed 8 times total.

A pairwise test.

Only tests all combinations of pairs of values.  Can yield a significant reduction in test cases compared to ordinary combinatorial tests while still obtaining great coverage.  See also:

[Test, PairwiseJoin]
public void Test([Column(0, 1)] int a, [Column("a", "b")] string b, [Column(false, true)] bool c)
    // Test something with the specified combination.
    // Will be executed only 4 times instead of 8.

A CSV data source.

Just one of many external data sources to be implemented.

[CsvData(ResourcePath="CsvDataTest.csv", HasHeader=true)]
public void ImplicitlyScopedResourceWithHeader(decimal price, string item)
    Log.WriteLine("{0}: {1}", item, price);

The data itself should be stored in an embedded resource called "CsvDataTest.csv".  We just create a file with that name in the same folder as the test class and then set its Build Action property to Embedded Resource in Visual Studio.

Item, Price
Apples, 1.00
Bananas, 1.50
Cookies, 2.00

Automatic data type conversions.

Can automatically convert strings into DateTimes and doubles into decimals for example.

Architecture Improvements

There were a number of internal architecture improvements in Gallio Alpha 3.  Here's a quick summary.

1. Unified Hosting Apparatus

In Gallio Alpha 2 there was some duplication between the responsibilities of the IHost and ITestDomain components.  These abstractions have been refactored.  As a result, ITestDomain was replaced by ITestDriver to handle the specific needs of setting up a testing environment.

The IHost abstraction provides a mechanism for Gallio to run code remotely such as in an isolated AppDomain or another process.

2. Pattern Test Framework Refactoring

There was an important piece missing from the data binding story in Alpha 2 that prevented certain kinds of parameterized tests from being expressed.  This has been resolved by refactoring of the Pattern Test Framework (from which MbUnit v3 is derived) and introducing the concept of a test data context.  IPattern is significantly simpler now.

This work also prompted the introduction of the Annotations mechanism  when it became clear that we needed a much more direct mechanism for reporting semantic errors in a test to the user.

3. Reflection Policy Enhancements

Introduced the concept of a typed ConstantValue for performing reflection over unevaluated attribute values.  For example, when populating tests for the ReSharper add-in we may encounter attribute values that are of type Type.  It's quite possible for those types to not be loaded in the runtime (since we're performing reflection against an in-memory code model).  So instead we can obtain a ConstantValue that represents the Type without actually loading it.

Gallio Alpha 3 also includes a Cecil-based reflection policy for scanning disk-based assemblies without loading them into the runtime.  The Visual Studio Team System add-in uses this policy to perform reflection without locking assemblies or introducing memory leaks.

4. Test Runner Redesign

The ITestRunner interface has been completely redesigned to make it easier to use and more versatile.  For one, the reporting functionality has now been integrated somewhat more tightly into the runner itself.  An ITestRunnerExtension can register new behaviors on a test runner using the ITestRunnerEvents interface.

5. Aggregate Test Drivers

Supporting test assembly configuration files is not as easy as it sounds.  For one, it requires us to create a separate AppDomain for each test assembly.  Then we have to somehow merge the test model and results.

Gallio Alpha 3 introduces an aggregate test driver to help with this.  However, the current design is still somewhat in flux.  I'd appreciate some feedback on how we can improve and simplify the test framework integration story overall.

Bugs Fixed

Here are a few of the bugs from Alpha 2 that have been fixed:

  • Icarus now unloads assemblies promptly to avoid locking them.  You can also enable shadow-copy mode for improved efficiency.
  • MbUnit v2 version compatibility problems fixed.  Should work with any version of MbUnit v2.4+.
  • Hung Gallio.Host.exe processes are no more.
  • xUnit.Net adapter has been upgraded to v1.0 RTM.
  • Installer PATH variable corruption.
  • Castle dependencies have been internalized to avoid version mismatches.
  • Default thread apartment state is STA and can be overridden with the [ApartmentState] attribute.
  • [Explicit] tests are now silent and do not display any output in reports unless explicitly selected, not even a message to say they are being skipped.  If you want noisy output, use [Ignore], [Pending] or [Annotation] instead.
Technorati Tags: ,

Monday, May 12, 2008

Openings at Ingenio


We're hiring!  Want to work with me?

To learn more or to apply, send an email with your résumé to

Also check out this link for more opportunities at Ingenio.

Platform Toolsmith

Do you love building tools?  Do you get a kick out of building integrated systems that just work?

Ingenio is looking for someone to help build a robust and highly integrated platform for software development, deployment and testing.   Our system consists of a mixture of web, telephony and data platforms so it takes a lot of ingenuity to assemble these pieces and to verify that they work together correctly to provide a compelling user experience.

We need an experienced toolsmith who understands the challenge of release engineering, system monitoring, infrastructure build-out and software architecture to help us keep our coders coding, our testers testing, our users using, and our systems running smoothly.

Sample projects:

  • Build new plug-ins for our distributed system monitoring application.
  • Develop a new deployment tool for coordinating updates to our server farm.
  • Implement a SIP phone emulator for testing telephony applications.
  • Plan SOA and ESB middleware deployment projects.
  • Work on Open Source projects such as Gallio, MbUnit, Archimedes and WatiN.

What we will look for in you:

  • You love to program!
  • You like to tinker and take things apart... and put them back together better than they were before.
  • You have great communication skills.
  • You know at least one object-oriented programming language such as C#, Java, Python, Ruby or C++.
  • You have experience with release engineering and deployments.
  • You have a 4 year degree in computer science or engineering.

Location: San Francisco, CA.  Downtown with easy access to BART and Muni.

Test Automation Guru (Lead)

Do you love testing?  Do you love working with testers, teaching them new tricks, designing systems and building tools?

Ingenio is looking for someone to lead our test automation effort.

Our system consists of a mixture of web, telephony and data platforms so it takes a lot of ingenuity to test that these pieces work together correctly to provide a compelling user experience.  There are many challenges involved in the construction of controlled test environments that can obtain reliable results and find bugs.  We need an experienced lead who thoroughly groks testing and can help us take test automation to the next level.

Sample projects:

  • Design a virtual automation test environment.
  • Build test tools and monitoring infrastructure.
  • Implement model-based and automated exploratory testing approaches.
  • Plan comprehensive automation test projects.
  • Mentor junior members of the test automation team.
  • Hire more smart people to work with.
  • Work on Open Source projects such as Gallio, MbUnit, Archimedes and WatiN.

What we will look for in you:

  • You have experience leading, teaching and motivating others to excellence.
  • You have a strong programming background.
  • You have great communication skills.
  • You know at least one object-oriented programming language such as C#, Java, Python, Ruby or C++.
  • You are familiar with at least one xUnit testing tool such as MbUnit, NUnit or JUnit.
  • You grok test automation.

Location: San Francisco, CA.  Downtown with easy access to BART and Muni.

Test Automation Wizard

Do you love programming and testing?  Do you enjoy writing high-quality code using the latest tools?  Do you hate bugs?  Do you like solving challenging system integration problems?

Ingenio is looking for test automation engineers to develop a comprehensive and maintainable test suite for our products.

Our system consists of a mixture of web, telephony and data platforms so it takes a lot of ingenuity to test that these pieces work together correctly to provide a compelling user experience.  We need talented tester/developers and developer/testers to decide what to test, to write tests and to adopt novel testing strategies.

Sample projects:

  • Write automated tests for our system using C#.
  • Implement model-based and automated exploratory testing approaches.
  • Build infrastructure for deploying, running and monitoring tests.
  • Plan comprehensive automation test projects.
  • Work on Open Source projects such as Gallio, MbUnit, Archimedes and WatiN.

What we will look for in you:

  • You love to program!
  • You are smart, passionate, eager to learn and get things done.
  • You have great communication skills.
  • You know at least one object-oriented programming language such as C#, Java, Python, Ruby or C++.
  • You are familiar with at least one xUnit testing tool such as MbUnit, NUnit or JUnit.
  • You have prior experience writing automated tests.

Location: San Francisco, CA.  Downtown with easy access to BART and Muni.

Test Automation Apprentice (Intern)

Do you enjoy programming?  Are you curious about test automation?  Do you want to get a head start in the industry?

Ingenio is looking for smart students to bring in fresh ideas, challenge the established order and remind us all to have fun.

Our system consists of a mixture of web, telephony and data platforms so it takes a lot of ingenuity to test that these pieces work together correctly to provide a compelling user experience.  As part of that effort, we officially sponsor the development of MbUnit, an Open Source testing framework.  We are constantly searching for ways to improve our processes.

We hope to learn as much from you as we promise to teach you.

Sample projects:

  • Create something new and fantastic that we haven't thought of yet in this list...
  • Develop a tool to automatically spider our web sites using C# and find bugs.
  • Write automated tests for our system using C#.
  • Build infrastructure for deploying, running and monitoring tests.
  • Create test reports.
  • Work on Open Source projects such as Gallio, MbUnit, Archimedes and WatiN.

What we will look for in you:

  • You love to program!
  • You are smart, passionate, eager to learn and get things done.
  • You have great communication skills.
  • You know at least one object-oriented programming language such as C#, Java, Python, Ruby or C++.
  • You are currently enrolled or have recently graduated from an accredited university.

Location: San Francisco, CA.  Downtown with easy access to BART and Muni.

Technorati Tags:

Google Code Download WTF

I was getting ready to publish Gallio Alpha 3 tonight but we're out of space on Google Code.

Ok, no problem... I'll just delete some stuff.

Google Code had other ideas:


Uhh... But I don't need this version anymore: I've archived it myself and I need the free space right now!

Meanwhile my request for more quota is still pending...

(I'm just glad I never wrote a script to upload nighty builds.)

Sunday, May 4, 2008

Another Programmer Bites the Dust

I've been struggling with Carpal Tunnel Syndrome for 6 or 8 months now.

I don't quite remember when it started.  I've had bouts of muscle tension on and off throughout my life.  After all, I've pretty much spent every other waking hour in front of a computer for the last 18 years or so (total of 22 years programming but during my early years I did not have a computer at home).  But recently I started noticing different symptoms.

  1. Numbness and tingling are now commonplace occurrences.
  2. It does not go away after a night's rest.
  3. It does not go away after a day or two of not using the computer.
  4. It has invaded other aspects of my life including cooking, recreation, sleep and sex.
  5. I find myself searching for ways to work differently and to avoid sustained typing or mousing.
  6. I find myself wishing for an eye-tracker and decent voice recognition to help out around the edges.
  7. It's made me cry...

I have already made many adjustments to my ergonomics and home life style.

  1. I use a keyboard tray tilted at a negative angle.
  2. I use a Microsoft Natural Wireless Ergonomic Keyboard and Mouse combo.
  3. I wear elbow braces during the day.
  4. I wear write braces during the night.
  5. I try to sit properly.
  6. My wife opens jars for me.

But it's still getting worse.

Today I installed Workrave to help remind me to take breaks, do my exercises and quit after working a long day.


Flip Side

I am now taking more active leadership roles.  I am a Lead Software Engineer at the office and the MbUnit / Gallio Lead on the side. 

There's just so much cool stuff to build out there!  And I know all sorts of smart people that I can set to the task of building it.  :-)

Friday, May 2, 2008

A Good Test Finds Bugs

This evening I found myself thinking about what my favourite test in Gallio must be.

It could be the formatter tests that are simple and to the point and leverage many of the good traits of the MbUnit Row-test, including generic method parameters.

It could be the MbUnit integration tests that self-host Gallio within itself to run tests and carefully analyze their output.


My favourite Gallio test is the abstract reflection policy exhaustive test suite!  It's not pure.  It's not pretty.  It's not tightly focused.  It's not short.  It's not precise.  It's not self contained  (it uses native .Net reflection as an oracle).  But boy does it find bugs!  All sorts of obscure deviations from expected behaviour in each of the 4 current reflection policy implementations.

It's an awful test but it does what a test should do: it finds bugs...

Technorati Tags: ,