Ran 2 miles today. It felt pretty good. The endorphins are running through my system! Of course in an hour I'll be exhausted.

I have been integrating NUnitAsp into a project here at work. It is nice although there are a few gotchas. The first is that the HttpClient that the framework uses is fairly stripped down. What this means is that JavaScript is not handled. This really isn't a huge drawback unless you are incorporating AJAX into the app. In my case I make an AJAX call back to the server when a user enters a Zip code. Since there is no JavaScript interpreter that call doesn't happen so That portion of the application cannot be tested in an automated way. In researching yesterday I looked at a information on FIT,FITNess, and Selenium which all seem to have a way to deal with that. I will have to look at them more closely.

The second Issue I am running into with the framework is that it doesn't maintain state. Of course this is expected for a unit test framework. Each test should run independant of the others. However it makes for some ugly setup and teardown in the tests when you have an application that uses more than one page. Especially when the pages assume that a previous page has been filled out. Still, It is nice to have even a rudimentary test that validation and basic actions are taking place. Also, I do not have to manually run through the application to make sure a change in one place has killed something in another place.

The only other Issue I have one is really somewhat minor but still kind of annoying. Testing controls that get rendered funny, like radio button lists is difficult. In creating a page I can add a radio button list to the page and assign options to it. When it is rendered it is presented as a table with cells each containing a radio button named "listname_choiceNumber" To test it I have to create a tester object for each choice. It just seems kludgy and cumbersome to me. Although it does work so I can't complain much.

In other news we are extending an offer to a new employee this week. It will be nice to get a new person in and to start really working as a team. I think once the new person is on board and situated we will take one or two days and do a "mini retreat." There are some goals and objective I want to set forth as well as some tools and methodologies I would like to start using. Both Josh and the new person both seem as excited about this as I do. That is really great and I think that bringing these about will make for interesting and more enjoyable development.