by atom » Thu Apr 26, 2012 8:24 pm
Hiya,
To me Unit tests are appropriate for continuous integration as they execute alot quicker than GUI tests
GUI tests should be run after a test build has been completed (rather than on each file check-in)
So you have a 2 layer automation stack:
1. Unit tests running in continuous integration giving developer quick feedback that code changes arent breaking their classes/methods
2. When unit tests passed and "QA" build done, execute the GUI tests
We use MSMQ to schedule and execute GUI tests across machines. We place details of what tests to run on the queue, then have a small Agent on each machine reading from the queue, and running the test.
Cheers