I love automated unit tests - part II

We recently reached the milestone of being feature complete in the web interface for Timeless 3.0. The next step was to create the installation so we could start our in house alpha testing during the development of the Windows version. But since we allow the choice of Access as a database option for small teams using the Windows version, we felt it was best to create the database and verify our business layer worked before integrating the SQL scripts into the web installation.

If you've ever developed an application to work with SQL Server and MS Access, you know there are differences. There are slight SQL differences, but the big one for us was differences in the way they handled paramertized queries. SQL Server uses named parameters and does not care about the order while the OLEDB provider for Jet only cares about the order of the parameters. As you can imagine this can cause significant testing.

Thankfully, our automated unit tests solved this problem. We still had to make the code changes, but it was a lot easier than trying to change it during UI development. It also meant we wouldn't be making changes to the web version during alpha testing just to accomodate Access in our Windows version.

As a side note, our test suite executes around 40,000 commands against SQL Server and around 42000 against MS Access.