Connecting to Cloud OCR vendors

OpenText Functional Testing connects to Cloud OCR vendors such as Google and Baidu to use text recognition services when running tests.

Set up a Baidu or Google Cloud OCR, and obtain an API to use for access. Configure OpenText Functional Testing's connection to the cloud OCR in the OpenText Functional Testing options dialog box or using an Automation Object Model (AOM) script.

In the options dialog, the API key that you enter is not displayed and you cannot retrieve it from the dialog box.
In an automation script, you must encode the API key before providing it in the script. To encode the API key, use the Password Encoder tool delivered with OpenText Functional Testing (<Installdir>\bin\CryptonApp.exe).

Note: The Password Encoder encodes the API key so that it is not visible in the script but does not encrypt it using a global encryption standard. The encoding is not considered or intended to fully secure the information.

The Password Encoder provides one-way encoding. It generates an encoded string from the API key you provide but cannot be used to retrieve the API key from the encoded result.

OpenText Functional Testing stores only the encoded string and does not display the actual API key anywhere.