About OCR Checkpoints

During the test run, TestComplete:

1. Gets the UI element, the text content of which you want to verify.

2. Recognizes text contents of the UI element using optical character recognition.

3. Checks whether the recognized text matches the expected value and reports the results.

You can add OCR checkpoints to your test during the test recording and at design time using the Create Checkpoint wizard. For detailed instructions, see Creating OCR Checkpoints.

If the recognized text content matches the expected value, the checkpoint logs the checkpoint passed message; otherwise, it logs the error message. The Details panel of the test log shows the sought-for text and the actually recognized text.

• If TestComplete can access internal properties of the needed UI element, use a property checkpoint to verify its text contents.

• If your tested application implements accessibility information using the Microsoft Active Accessibility (MSAA) engine or the Microsoft UI Automation framework, you can configure TestComplete to use that accessibility information to get the content of the needed controls and use a property checkpoint to verify it.

• (For Windows desktop applications only) If your tested application uses the WM_PAINT, WM_PRINTCLIENT, or Direct2D library to render its text content on the screen, you can use Text Recognition to access the rendered text and the property checkpoints to verify it.

• If TestComplete cannot recognize the text content of your tested object properly or to verify how your tested application’s user interface looks on the screen, you can use a region checkpoint.