Some API monitors are failing while some are passing. The errors seem to be location-dependent.
Our remote locations run either Test Runner 1.1.0 or 1.9.0 to run the soapUI/Ready!API tests.
TestTunner runs functional soapUI/Ready!API tests from the command line.
We have kept some of our monitoring locations at 1.1.0 due to certain factors related to customer’s API projects that were created with earlier versions of soapUI/Ready!API.
As of this writing, the locations that are still running TestRunner 1.1.0 are:
Dallas – XO
Manchester – UK
Los Angeles – Level 3
New York – Peer 1
Please note that this information is subject to change.
All of our other locations are running TestRunner 1.9.0.
It normally does not make a difference which version of TestRunner is used; however, if you are seeing errors only from locations running 1.1.0, please change to locations running 1.9.0 (as well as the reverse.)
Please review the following video to see the API Run Log examined to determine which version of Test Runner is being used.
Ready API TestRunner 1.1.0 and 1.9.0 Run Logs
https://vimeo.com/235773064
This Post is due to an actual Customer Care case, and a Knowledge Base article was created.
Also, if your issue cannot be solved through information on this Forum or from the Knowledge Base, please open a case with Customer Care through:
http://support.smartbear.com/message/?prod=Alertsite
In this manner a case will automatically get generated into the Customer Care queue and be addressed in the most efficient manner.
