Using server-based testing has several benefits that could justify the time investment for your team. If you're on the fence about whether going this route works for your team, make sure to consider the following in your evaluations:
Moving your builds and unit tests to a server frees your local box to keep working on features and debugging, while your builds and test suites run remotely.
Build triggers can run your tests on code check-ins and alert your team when things change expectantly due to tests failing.
Tests on your server are consistent and run the same way each time; meaning that individual developer environment and project tweaks won't affect test runs.
You can schedule full test suites to run at your convenience and short running tests to execute on every code check-in as an example.
You can have your tests executed against multiple development environments and hardware. For example, you could have your test run on multiple iPad models...
