Hi Henrik,
I want to write some data related to the test case run into a file. These are technical data like timestamps of some test steps and an identifier of the test case run as well as business related data related to SOAP requests (there are several SOAP requests in the test case). Maybe the SOAP response should be logged, too, if there was a failure, but maybe these failures will be logged separately after the according test step has finished.
A test case run should be stopped if one of the test steps is a failure, to avoid subsequent errors.
Therefore I cannot just use a Groovy test step instead of an event handler.
However, I see a possibility how this can be done: I could configure the test case run to continue after failures and I would have to use "gotos" to skip test steps if a failure has occurred. The target test step of the gotos would be e.g. the last one, where all the logging would be done. This would not be very understandable and I don't especially like this idea.
Do you have another suggestion?
By the way: Are the "TestRunListener" events, e.g. "afterStep" usable with loadUI? These could be used for logging the failures after the according test step as I described above.
Thanks and regards
soapLoadUser
