selkind
16 years agoOccasional Contributor
teardown script runs after runner.waitUntilFinished() notified?
Are load test teardown scripts run after the load test signals any listeners that it's done?
I have a "master" load test whose setup script runs three child load tests in sequence - waiting for each to complete with WsldLoadTestRunner.waitUntilFinished() before starting the next.
In each child test, its setup script resets the statistics in a back end before the load test starts. Its teardown script sleeps for 2 minutes to wait for the backend's statistics to be collated (done every two minutes), then collects the statistics from the backend.
What I'm seeing is the the next child load test is already executing before that sleep is up - so that the statistics when collected are polluted from the next load test.
I have a "master" load test whose setup script runs three child load tests in sequence - waiting for each to complete with WsldLoadTestRunner.waitUntilFinished() before starting the next.
In each child test, its setup script resets the statistics in a back end before the load test starts. Its teardown script sleeps for 2 minutes to wait for the backend's statistics to be collated (done every two minutes), then collects the statistics from the backend.
What I'm seeing is the the next child load test is already executing before that sleep is up - so that the statistics when collected are polluted from the next load test.