Timeouts can occur if there are slow or a lot of tests to run. As of CodeScan version 3.5d you can choose to run the tests in two new modes:
- async - tests are queued and the results polled until completion. Tests are run in batches of 200 classes.
- history - previous test run results are used. In this mode, test data may be old or non-existent
You can solve timeout problems by changing the Unit Test Timeout setting
sf.test.timeout in Administration > Configuration > General Settings > CodeScan to something larger. This parameter’s default setting is one hour (3600 seconds).