Forum Discussion
Also attached the exportLog() implementation.
- tristaanogre6 years agoEsteemed Contributor
What you have described is correct behavior. Basically, the OnLogError event handler interrupts that act of logging the error. The error is not written to the log until the event handler exits. This is to allow the event handler to make any necessary modifciations to the error (or skip it entirely) before it is written to the log.
Rather than the SaveResultsAs going into that event handler, I'd actually put it in the OnStopTest event handler.
- nisgupta6 years agoValued Contributor
Thank you for the updates
If we look at the screenshot we are putting the SaveResultsAs into OnStopTest event handler I am calling the function exportlog which is in in the OnStopTest event.
Then also we are having the issues.
Thanks
NG
- m_essaid6 years agoValued Contributor
Hi nisgupta
I think I organize myself differently.
I have several tests within a Project. Each test stops at the first error that occurs, but the Project is not set to "stop on error". I could test the feature A, B and C of my application in respectively the test A, B and C.
I add a last test item in which I only prepare my mail, prepare my log with the scope of the whole project.
If A and C go OK and B goes not OK, I'll have 4 test items in my log : A, B, C and the last test item in which I write the log and send my mail.
Every item is loggued entirely (until any eventual error, of course).
Mind the call stack of the last item in error in the report to see everything.
I hope this will help,
Mehdi
Related Content
- 9 years agom_essaid
- 8 years agoMulgraveTester
- 11 years agoArmandsBruns
- 8 years agoDonN
Recent Discussions
- 22 hours agoGane195