Forum Discussion
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
That look like we need to create one test items for logging and exporting for every projects , right to make the things work ?
- nisgupta6 years agoValued Contributor
Any other suggestions ?
- m_essaid6 years agoValued Contributor
well, I don't know how do you organize yourself but my projects coult contains 40 or 50 test item and could need 4 hours of playback so one item for each is not a problem.
- nisgupta6 years agoValued Contributor
I follow your strategy . Seem like for now it look fine, and I can now see the errors in exported MHT report I have attached the screenshot - TClogseetinga and TClogsetting.
Also attached the TCProjectlog.
Let me know
Thanks
Ng
- m_essaid6 years agoValued Contributor
yes that's it, you could see a test which is always "green" (it's the last test), but I don't really use the pie in the report.
please mark post as solution if you accept it :)
Related Content
- 9 years agom_essaid
- 8 years agoMulgraveTester
- 11 years agoArmandsBruns
- 8 years agoDonN
Recent Discussions
- 2 days agovladd1