Forum Discussion
SmartBear_Suppo
Alumni
12 years agoHi again,
I seem to have misunderstood your problem then - sorry for that. I haven't been able to reproduce this issue yet, so if you could send me a small project where this occurs, that would help.
Meanwhile, a suggestion for a workaround to avoid using TearDown scripts is to set your TestStep failure message as a property instead using groovy, and then retrieve those properties' values in the calling groovy script. Does this make sense?
Regards,
Arian
SmartBear Sweden
I seem to have misunderstood your problem then - sorry for that. I haven't been able to reproduce this issue yet, so if you could send me a small project where this occurs, that would help.
Meanwhile, a suggestion for a workaround to avoid using TearDown scripts is to set your TestStep failure message as a property instead using groovy, and then retrieve those properties' values in the calling groovy script. Does this make sense?
Regards,
Arian
SmartBear Sweden