Forum Discussion
That works for specific tests, but for something like "Object not found", I don't think there's a way to have TestComplete sort out why the failure happened. It could be either of those reasons.
If, as the original post mentions, the goal is to separately 'see' requirement failures and other failures, the solution I proposed works. An 'Object not found' error can lead upto a requirement failure message only if I explicitly post that message, else it gets filtered out in my log.
Obviously for debugging purposes, you will have to remove the 'REQ' search condition to see what other errors occured. Customization of the log is neccessary since there is no way for TC to tell when a requirement fails.
- Marsha_R9 years agoChampion Level 3
Which is exactly my point. TestComplete can't know. :)
- Ravik9 years agoSuper Contributor
TC should have such machanism.
- Ravik9 years agoSuper Contributor
I think we may achive this kind of result by implementing "Event" (On Error, On Stop).
In On Error/On Stop Event we will specifying system errors like - File NOT,Object NOT found,Array Index out of bounds. If any error occured then log those as a system failur error with a specific prefix.
Related Content
- 9 years agoDavidLunn
- 6 months agosohailalam2696
- 3 years agofdelmoro
- 12 months agosinis
Recent Discussions
- 5 hours agoSubhraDas
- 18 hours agoJacobjacob44