Here are some different ways you can handle error messages
https://support.smartbear.com/testcomplete/docs/testing-with/running/control-test-flow/index.html
I wasn't quite looking for error handling when errors occurred in the test. While I am running a UI test, I would like for testComplete to monitor the Network area of the browser (in the developer tools of chrome). If a failure status shows up (such as a 400 or 500 series http response code), then TestComplete would push that onto a stack or write it to the log as a 'Warning' message. Even though you get a 400 or 500 response in the network tab, this doesn't mean the test is going to fail. So, a test could pass, but there were some glitches with the website that the TestComplete test wouldn't catch if it weren't monitoring the network traffic (the http response codes).
Hi,
No, I am not sure this can be done now in TestComplete.
While this seems to be a useful feature (but why stick to Chrome only and not to request the same functionality for all browsers that provide developer tools?) and one can create a feature request via https://community.smartbear.com/t5/forums/postpage/board-id/TestXCompleteFeatureRequests, I would say that requests monitoring is rather from integration and/or load testing areas.
A possible approach with TestComplete to monitor request results is to use some proxy (ProxyMob, Fiddler?), set your tested application to send all traffic through this proxy and then request proxy if some requests ended with 4xx or 5xx result codes.
