AmpTools.Net

You can find many of the new features over at Jeff Brown's blog.  Some of the cooler features of note is the integration with the visual studio testing system, wrapping testing for exceptions into a delegate, and data store called Ambient, in which you can store state for your tests.  I've integrated this into amplify which is again, now on GitHub. I did run into a few lil issues when setting this up though....

The biggest issue was finding out how to turn a project into a test project in order to get the visual studio integration working for Gallio. Basically you need to make modifications to the .csproj file and add an XML element of <ProjectTypeGuids> into the first <PropertyGroup> of the file. 

<ProjectTypeGuids>{3AC096D0-A1C2-E12C-1390-A8335801FDAB};
{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC} 
</ProjectTypeGuids>

After this, I could get the Gallio tests showing up in visual studio.

Now this coupled with Test Driven .Net really helps with the testing process especially since with certain versions of Visual Studio, Test Driven .Net will let you run visual studio's code coverage with Gallio.

Again, one of the cooler features was the improvements to Mb-Unit's Asserts (which did change the API, but its all good, cause I wrap the Asserts that I use in BDD style mixin Methods, so I just need to change them in one place). The one really change of note would be adding Assert.Throw and Assert.Throw<T>, to which you can wrap throwing an exception into a delegate.

All in all nice improvements to both Gallio and Mb-Unit, which are now incorporated into amplify.

Labels: Amplify, BDD, BHAG, C#, Code, CSharp, Gallio, Mb-Unit, Mixins, Unit Testing

After getting cygwin updated, and getting much of my dev stuff on a USB drive for many good reasons and exploring using git on windows.  I've decided git is stable enough to use, a good reason for me to use the command line more often and git fits more of my development needs. 

The biggest factor is that it is its own repo on my local, so when I'm working disconnected, i can still make commits to my local drive.  The second biggest reason is the amazing merging, branching and speed at which it works. 

Also with the code move, I'm starting over per-say, by slowly adding code only after tests are written for them, this process will put me back some, but when down, I should have a decent size test suite for amplify which is sorely needed. 

Of course another while doing all of this I also moved a huge portion of my dev environment to my USB drive to recently having to develop on a desktop not provided for.  I was even able to get e-texteditor on a USB drive without using something like thinstall/thinapp. 

As for moving to GitHub, well there are not that many hosted repositories for git at this point and you really can't beat free.