VReplogle
17 years agoOccasional Contributor
An always run capability
Hello,
Perhaps the functionality doesn't exist, but is there a way to have a 'cleanup-type step' that always gets run in any particular test case even if a previous step fails for whatever reason?
example:
test case x
step 1 - create a record
step 2 - pass the generated key to step 3 && 4
step 3 - validation that shouldn't fail (but currently does)
step 4 - delete the record
test case y (that expects test case x to have cleaned up after itself)
...
Notably, one solution seems that we could 'pull out' whatever should always happen into an extra test case (in-between test case x && y) but that would effectively nearly double our number of test cases and be less readable in the end.
Is there another SOAP U.I. alternative that could always run step 4 for x regardless of soap faults and other means of failure? If not, should I log that as a feature?
Thank you;
--V
Perhaps the functionality doesn't exist, but is there a way to have a 'cleanup-type step' that always gets run in any particular test case even if a previous step fails for whatever reason?
example:
test case x
step 1 - create a record
step 2 - pass the generated key to step 3 && 4
step 3 - validation that shouldn't fail (but currently does)
step 4 - delete the record
test case y (that expects test case x to have cleaned up after itself)
...
Notably, one solution seems that we could 'pull out' whatever should always happen into an extra test case (in-between test case x && y) but that would effectively nearly double our number of test cases and be less readable in the end.
Is there another SOAP U.I. alternative that could always run step 4 for x regardless of soap faults and other means of failure? If not, should I log that as a feature?
Thank you;
--V