I have found where ALM displays the status of a test as passed, but in the Run Results file, the status displays as failed when running API tests. It seems that values in an array that have a failure for a checkpoint are not reflecting correctly in ALM when clearly it shows failed. This is affecting multiple users in multiple projects when running tests with an array type of validation in the check point. Any other test that fails, reports up to ALM correctly. We are currently using ALM 12.01 with UFT 12.53 with No patch, and we are having to manually change the status from ‘Passed’ to ‘Failed’ in ALM in order to mark tests that have failed.
Answer by jameslcoleman · Nov 21, 2016 at 09:43 PM
This is a known issue with HP, and it is currently under review and being investigated by their development team. In the QCCR, it states that when creating an API test in UFT and using CheckpointEventArgs to define a new Checkpoint, the result in the report is failed or success by executing from UFT depending on input parameter. The test status displays as passed when run from ALM, but displays as failed when run from UFT.
You can view the QCCR by clicking the following link:
SQL Queries in API 2 Answers
ALM API via Python 1 Answer
Automation API for UFT API-Testing 1 Answer
Can't create API Test 1 Answer