Applies to TestLeft 4.10, last modified on May 28, 2019

This topic describes the changes made to TestLeft 2.50. For information about the changes in other TestLeft versions, see TestLeft Version History.

Support for BDD

You can seamlessly integrate TestLeft into your behavior-driven development workflow. TestLeft comes with several sample projects that demonstrate how you can convert Cucumber, SpecFlow or JBehave BDD scenarios to actual test steps. See About Behavior-Driven Development.

Java Support

You can now use TestLeft to create automated functional tests in a Java IDE of your choice. You can run these tests from Jenkins, Maven, Java unit testing frameworks, from your Java IDE, or in any other way.

TestLeft UI Spy supports generating Java code for object identification and method calls. You can also run UI Spy as a standalone executable (<TestLeft-folder>/Bin/SmartBear.TestLeft.UI.Spy.exe).

To get started, see the TestLeft for Java Tutorial.

Support for Electron Applications

You can use TestLeft to create and run automated tests for Electron-based desktop applications. The test engine recognizes individual controls in these applications and their types, provides access to their native members, and offers special methods and properties to simulate user actions on the controls with ease.

To test Electron applications, you should launch them from your tests using the Driver.Applications.Run(…) method (Driver.getApplications().run(…) in Java). For details, see Preparing Electron Applications for Testing.

Overall Improvements

  • Improved TestLeft UI Spy:

    • Formerly, UI Spy was available as a panel of the Visual Studio IDE. Now, you can also run it as a standalone executable: <TestLeft-folder>/Bin/SmartBear.TestLeft.UI.Spy.exe.

    • UI Spy supports generating Java code for object identification and method calls.

  • New sample projects. TestLeft includes a number of new sample projects that demonstrate how you can create data-driven tests, integrate TestLeft with image-comparison systems like Applitools or Sikuli, or integrate it with BDD systems like SpecFlow. See TestLeft Samples for details.

  • Support for attached properties in WPF applications. TestLeft can now expose attached properties of WPF objects, so you can see these properties in the UI Spy and use them in your tests through the IObject .NET interface or TestObject Java class.

    The names of attached properties have a syntax like Attached-Property-Provider_Property-Name, for example, DockPanel_Dock.

    UI Spy shows attached properties with non-default values only (those that are explicitly defined in the application's source code). UI Spy does not display attached properties with default values, although, you can use them in your tests. Attached properties with identical names, but with different namespaces and assemblies are not supported.

  • Support for the latest available CEF version. You can now create and run automated tests for applications that use Chromium Embedded Framework ver. 3.3282.1741 and earlier.

  • TestLeft now supports Infragistics UltraComboBox controls ver. 2017 Vol. 1. It recognizes these controls as combo boxes and provides specific methods and properties to simulate user actions on these controls.

  • Updated test log view:

    • The TestLeft log has the new Time Diff column. It helps you find out how much time passed between messages during the test run.

    • Test results exported in the HTML, MHT or XML format now include summary information on the test run. This information includes the start time of the test run, the end time, the test duration, the number of warnings and errors and the name of the computer where the test was run.

    • You can now filter messages in the exported HTML or MHT log by the message type.

      In addition, you can use the new Search box to find messages by their contents. When you type text in this box, the log will filter the messages and display only those that contain the typed text.

  • Smarter Close methods. The default timeout of the Process.Close() and Browser.Close() methods has been increased from 3,000 to 60,000 milliseconds. The method now also checks for the “Do you want to save the changes?” window and similar ones, and stops waiting for the process to exit, if any.

  • You can now create and run automated functional tests for web pages opened in Chrome 65 and Firefox 59.

  • To improve the Firefox performance, TestLeft now automatically configures some Firefox settings when you launch the browser from your test, or when your test opens a page in the browser. See the Mozilla Firefox - Browser Settings section in the Preparing Web Browsers for Testing topic.

  • TestLeft now supports Qt controls version 5.9.

  • The TestLeft installer uses a newer InstallShield version. When installing TestLeft in silent mode, you can use the /clone_wait argument of the InstallShield command line to wait for the installation to complete. See Installing TestLeft in Silent Mode.

  • We have fixed a number of bugs reported by our customers.

Discontinued Support

  • Since version 2.5, we stop supporting Microsoft Internet Explorer 9. We will no longer run tests for this browser and will not provide bug fixes for it. You will still be able to run web tests using Internet Explorer 9, but we do not guarantee these tests will work properly.

See Also

Introducing TestLeft
TestLeft Version History

Highlight search results