Forum Discussion
enliven
16 years agoContributor
We primarily use the testCase.TearDown for cleaning up data. The issue is that we dont want the case.TearDown to run with every iteration of the LoadTest for the testCase.
I thought about using the setup of the loadtest to get current then set the wsdlTestCase.TearDownScript ="", then put the original back during loadTest.TearDown but didnt like that idea.
What I have done is to convert the testCase.tearDown into a testStep which is disabled/enabled during the loadTest.Setup/TearDown (respectively). Now I just need to be able to run that specific testStep during loadTest.TearDown so I dont have to run them manually after performing said loadTest.
hmm... I suppose I could copy the groovy from the testStep['TearDown'] into the loadTest.TearDown but would prefer to avoid that as it will be alot more code to manage.
I thought about using the setup of the loadtest to get current then set the wsdlTestCase.TearDownScript ="", then put the original back during loadTest.TearDown but didnt like that idea.
What I have done is to convert the testCase.tearDown into a testStep which is disabled/enabled during the loadTest.Setup/TearDown (respectively). Now I just need to be able to run that specific testStep during loadTest.TearDown so I dont have to run them manually after performing said loadTest.
hmm... I suppose I could copy the groovy from the testStep['TearDown'] into the loadTest.TearDown but would prefer to avoid that as it will be alot more code to manage.