Forum Discussion
Actual what we need is that we should be able to distinguish between the two types of failures in the output graph:
1. Failure due to any random issue (where requirement execution was interupted by some system issue).
2. Requirement failure (application under test did not work as per requirement).
The way I do it is by customizing log messages:
1) For requirement fail condition: I log messages to the project log as below
Log.Error("REQ:" & log_message) where log_message is a message string that I want to show e.g. "Email address not verified"
2) For requirement pass condition: I log messages to the project log as below
Log.Checkpoint("REQ:" & log_message) where log_message is a message string that I want to show e.g. "Login success message displayed"
Then, we can filter the log as shown to display only the requirement failure and success messages.
Since we are adding the search condition ('REQ'), any other non requirement related issues will not show.
- Marsha_R9 years agoChampion Level 3
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.
- djadhav9 years agoRegular Contributor
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. :)
Related Content
- 6 months agosohailalam2696
- 3 years agofdelmoro
- 11 months agosinis
- 9 months agoMSL
Recent Discussions
- 7 hours agovladd1