Unit testing in MS Access

Question

I have an Access database project that is getting a bit to large to try to keep track of in my head. I know it is a little late in the game, but better late than never right?

Answer 1

Personally I think with a combination of the excellent access FE auto updater

http://autofeupdater.com/

And a UAT environment that is either linked into the live data or testing data that should catch most of the problems. I’m also a sole access developer and my model consists of

• dev land where I make changes

• UAT land where a select few users test the changes and approve

• Live land where everyone else lives

The key difference I see between projects is the capability of the people doing the UAT. I had one major release which was migrating from an access back end to SQL server, I sent the email saying that the version was in UAT ready for testing and got one back 30 minutes later saying it had all been tested (impossible) low and behold there was a bug in a very common area.

So in conclusion, set your staged environment up and pick your testers well!