Well, the holidays have come and gone. Thankfully. Everyone is getting back to work, picking up where they left off mentally, a few weeks ago.

A lot has happened over the past few weeks for me. First, new PC. Here are the specs

P4 3.0Ghz w/HT
1GB Ram
200 SATA HD
ThermalRight[^] XP-120 Heatsink w/120mm fan pushing 130 CFM
Sony DVD+-RW w/Dual Layer

Unfortunately for anyone reading my blog (me), I also picked up a few games, and they seem to be taking up a fair amount of time. Waiting for the DVD drive to show up so I can install UT2004 Editors Choice Edition, however I have been playing Thief: Deadly Shadows and Railroad Tycoon 3. Both games are pretty good, but I don't see myself finishing either of them any time soon.

On a side note here, I see that there is some sort of public engine for UT2004. I also read a few posts talking about requesting data from HTTP calls within the UT2004 engine. I will really need to look into this once I get the game installed.

Over the past couple weeks I have continued reading Martin Fowlers Refactoring book. At this point I am skimming through the catalog, reading sections that I see myself using, or suggesting other developers use.

Oh, I almost forgot. I stumbled across this link[^] the other day, and it lead me to find a sweet tool called RUnit[^]. Basically what RUnit does is allow you to use a web GUI to run your unit tests. For me, the benefit of this comes when you are working with a web framework that is utilized by multiple projects. I am working on a couple projects that are utilizing the same base framework, but each have their own Biz layer and UI layer. For the most part, the framework serves as the DAL, however, project specific pieces of the DAL may be located in the Biz layer. Anyways, I'm getting off topic.

With RUnit, I was basically able to setup one web project, and include all of our existing NUnit tests into one project. I organized it in such a way so that it is clear to the developer what tests group they need to focus on while working on a project. However, since all tests are in one project, and one aspx pages actually runs the tests, the developers and/or testers have one place to go to run all unit testing. In a roundabout way, this also supplies us with a small bit of regression testing since we are able to run NUnit tests for projects we may not be touching, but that are using the same base framework that we may be adding functionality to, or refactoring. This testing project will now replace our standard testing project within each sub projects solution.

In the end, I was very happy with RUnit, and the added functionality it provides for NUnit testing.