Forum Discussion
Any update on this problem?
- scot196711 months ago
Champion Level 3
Could this be related to the last release of TE? Check the latest reported issue here in the community. The last comment about warnings and errors makes me think it may be related...
testFiltercriteria not applied | SmartBear Community
- mhoult2211 months agoOccasional Contributor
Thanks for the link scot1967, I hadn't seen that issue. I guess it could be related (certainly it won't help!), but we've had the Warnings as Errors issue for 2 years now, and the linked issue relates to the latest test adapter version.
We've also got a support case raised with Smartbear for the new adapter (#00678070), as it is showing all test steps in a test plan as failed if only a single test step fails. This makes ADOs results totally inaccurate. Only if a test plan has a 100% pass rate does it show as passed, else it will show every single step as failed.
- mhoult2211 months agoOccasional Contributor
Hi. Our original support case was closed as we thought the issue was resolved, but it came back. We have a new case: # 00691802. It's status is: Waiting on SmartBear (Awaiting Fix)
From some investigation it seems the reason we thought it was resolved was because of the "TestComplete test adapter installer" setting reportAnyError.
In a test we did, with reportAnyError=false we see two errors. One correctly from Log.Error, but also one from Log.Warning, which is incorrect.With reportAnyError=true, the only "error" is from Log.Error, as expected, but none of the Log.Warnings show in the Azure pipeline, they are showing as "Passed", which is incorrect.
So we waiting now to see if Smartbear have a fix.