> > It reports script failures as test failures, which is incorrect.
> Hm-m-m... Why not?
Good question.
I need an accurate measurement of the quality of the application for management reporting.
When I mix together test script failures with application test failures I get unrealistic numbers. For the application I am testing I need to know how many tests are we performed, how many failures there were, how severe the failures were, how many planned tests were not executed, and what aspects of the application were tested.
I only need to know how many script failures occurred if I am going to track issues for test script development.
For management reporting, combining the two types of failures into a common log creates an unrealistic assessment of the quality of my application.
So I am wondering how other people break out those measurements when using Testcomplete.
