Hello Will,
Currently, the aqEnvironment.RebootAndContinue method generates individual logs for all parts of the test - this is the expected behavior.
We have an appropriate suggestion to make a single log be generated when using the RebootAndContinue method, and your request has increased its rating. Thank you.
Meanwhile, to work around the RebootAndContinue log restriction, you can try exporting test results generated before and after the reboot and then parse the exported results to combine them. Please see the [url= http://smartbear.com/support/viewarticle/10992/]Exported Results Structure[/url] Help topic for information on the test results structure.
Or, you can create a distributed test. TestComplete allows running tests distributed among several computers, as well as rebooting remote computers. So, you can create a distributed test and organize it in the following way:
1. The master computer starts a test on a slave computer and reboots it after the test run is over.
2. After the slave computer is rebooted, the master computer starts another test on the slave computer.
3. All logs of the tests performed on the slave computer are copied to one log on the master computer.
For more information on distributed testing in TestComplete, please see the Distributed Testing - Overview Help topic.
By the way, the RebootAndContinue log restriction and possible workarounds were discussed in the following forum thread:
http://smartbear.com/forums/forum/post.aspx?mode=singleThread&thread=57caf5f6-5d44-4632-acf3-eeb44c081be2.
Please let us know if you have any additional questions.
Thank you.
