Forum Discussion
wfetherolf
14 years agoOccasional Contributor
I've come up with a workaround for this issue.
I created a Network Suite, and set it up so that there are two sections of the test, one section for before the reboot, and one section for afterwards. Each section is in it's own job in the network suite, and they're executed against the same host. The first section is set to reboot the host when it completes. In between the two sections, I've got a function that waits for the host to come back from rebooting. If you don't wait for the host to come back, the master project will attempt to execute the second job on the host as soon as the first job completes, but because the first job has initiated a reboot, the second job won't be able to start. The network suite will aggregate the logs for the two sections for us, and give us an overall success or failure state for the test. This will probably work for the rest of you until SmartBear gets the RebootAndContinue functionality updated.
I created a Network Suite, and set it up so that there are two sections of the test, one section for before the reboot, and one section for afterwards. Each section is in it's own job in the network suite, and they're executed against the same host. The first section is set to reboot the host when it completes. In between the two sections, I've got a function that waits for the host to come back from rebooting. If you don't wait for the host to come back, the master project will attempt to execute the second job on the host as soon as the first job completes, but because the first job has initiated a reboot, the second job won't be able to start. The network suite will aggregate the logs for the two sections for us, and give us an overall success or failure state for the test. This will probably work for the rest of you until SmartBear gets the RebootAndContinue functionality updated.