Add a sane per-test timeout #32
Description
It's possible that some tests might time out, particularly when we're using third party testing systems like Sauce Labs.
It would probably be beneficial to set timeouts for the tests in the main tests project, so that if they are taking too long, they are cancelled. This will help prevent tests which get stuck and hold up others.
A good timeout should be researched. As a starting point, two minutes should be plenty of time. But actually one minute should suffice.
The timeout needs to allow sufficient time for the connection to Sauce to work etc. Whilst Sauce Labs might only report a single test as taking a few seconds, it actually takes a lot longer than that in reality.
It might be useful to do a full test run against Sauce Labs locally, and analyse the times taken from the NUnit test results XML.