Applies to TestLeft 4.30, last modified on November 21, 2019

In TestLeft 2.31, the following bugs reported by our customers have been fixed:

  • Fixed: TestLeft installation was unable to detect Visual Studio 2017 if Visual Studio updates were installed on the computer.

  • Fixed: On Windows 10 Creator Update, objects could be recognized incorrectly if recognition was performed via UI Automation (for instance, the NativeUIAObject.Name property could return an incorrect value).

  • Fixed: Some objects in the object hierarchy of an application recognized by using UI Automation could be duplicated.

  • Fixed: TestLeft could fail to recognize all grid rows in an application recognized by using UI Automation.

  • Fixed: The NativeVBObject.Name object returned the "Parameter not optional" error.

  • Fixed: TestLeft UI Spy could report errors when exploring 64-bit applications compiled with Delphi Tokyo 10.2.

  • Fixed: TestLeft could fail to call properties and methods added to a TStringGrid control in applications compiled with Delphi Tokyo 10.2, because the application’s debug information was read incorrectly.

  • Fixed: During the test run, TestLeft could stop recognizing some Windows Forms controls after the application froze.

  • Fixed: TestLeft failed to recognize controls by using the Text Recognition technology if text characters in the application were associated with glyphs by using the IDWriteTextAnalyzer::GetGlyphs method.

  • Fixed: When the Firefox web browser was running in multi-process mode, TestLeft could fail to recognize web pages correctly.

  • Fixed: Firefox could exit unexpectedly when accessing the Page object.

  • Fixed: TestLeft identified object coordinates in the Edge web browser incorrectly.

  • Fixed: When capturing objects in a CEF application by using TestLeft UI Spy, the application could stop working.

See Also

What's New in TestLeft 4.30

Highlight search results