Automated Unit Testing

I have a confession to make.

I haven't been writing testing code for my designer service web application.

THE HORROR!!!

:)

This designer service is my first Ruby on Rails app. I've been learning both Rails and Ruby during the development of it. I'm finally feeling pretty comfortable with the structure of everything. (At least the way I'm doing everything. ;) )

Now that I've got my head wrapped around how to put everything together, and a big chunck of the app completed I figured it was a good time to get into the built-in testing of Rails.

On the Java side I've worked with JUnit before, and thought it was pretty cool. So far, it appears that most of the Rails stuff is very similiar. Especially when using the Eclipse-based IDE, RadRails. It uses the same (or a very good knock-off) testing GUI as Eclipse does for JUnit.

The one thing I found with Rails that I'm not sure there is an equivalent for on the Java side (at least not as simple to setup) is something called, fixtures. Fixtures are pretty neat. They setup your test database with the test data you specfiy simply by typing the values into a text file (the "fixture" file).

I want to thank the guy(s)/gal(s) who wrote up the manual on Rails testing. It helped out big-time.

As I did tonight, I'll be spending my next couple of working sessions building up my test cases.