It seems intuitive that the teardown script is intended to do cleanup work for the test case or test suite after it executes. Have you tried this code in other scripts - like a requestFilter.afterRequest event handler or a groovy step? Maybe by the time teardown occurs a rerun of the test might have unpredictable results.
I think of scripts running in this order
1. Test Suite (setup script if it exists )
2. requestFilter.filterRequest (if the event handler exists)
3. Test Case (setup script if it exists)
4. Groovy Step (groovy script if it exists)
5. requestFilter.AfterRequst (if the event handler exists)
6.. Test Case closure (Assertion Script -if it exists)
7.. Test Case (teardown script if it exists)
8. Test Suite (teardown script if it exists)
Of course there are other event handler scripts but I normally work with the request filter events.
I have been able to use the afterRequest and access the response and rerun a request.
Bill
