Migrating Projects Created in Earlier Versions to TestComplete 12

To upgrade your test project to the current TestComplete format:

• Open the project in TestComplete.

• TestComplete will show a message informing you that it is about to convert your project to the new format and asking for your approval.

• If you have not created a backup of your project, click Backup and Convert (recommended).

  A project can include references to project items that are located outside of your project folder. For instance, your project can refer to a keyword test or script unit that belongs to another project suite. TestComplete converts these “external“ project items to make the new project functional. However, it does not create a backup copy of them. You have to back up these items manually. Otherwise, you will not be able to open them in earlier TestComplete versions.

  If you do not need a backup copy of your project, click Convert.

• TestComplete will convert the project to the new format and open it.

Depending on the project structure and on the TestComplete version in which the project was created, you may need to make additional changes to your project. See the upgrade notes below.

Some notes for source control users:

• When converting a project that was bound to source control, TestComplete asks you to specify the information needed for connecting to the source control system and working with the project (such as the user name, password and the project folder).

• The upgraded project may include new project items and files. If you use source control, select the Bind new items to SCC automatically option in Tools | Options | Source Control to add these files to source control. You can also add new files to source control manually (see Binding Test Projects to Source Control (Legacy)).

• Earlier versions of TestComplete worked with source control systems via SCC API Providers. These APIs are compatible with a wide number of source control systems, however they offer a mediocre level of integration.

  Starting from version 11, TestComplete has dedicated plugins which provide a higher level of integration with Subversion, Git, and Mercurial.

  If you store your projects in these source control systems, we recommend that you use newer plugins instead of the legacy SCC API Providers. To learn how to switch a source control provider after the project was converted, see Migrating From Legacy SCC API Providers.

If you run test projects on a schedule or from a continuous integration system, you can convert them to the TestComplete 12 format automatically. To do this, specify the /SilentMode and /ForceConversion arguments for TestComplete 12.

TestComplete 12 will not run unconverted projects.

TestComplete versions prior to version 12.60 included the Optical Character Recognition (OCR) engine that could capture and recognize text rendered on the screen. Starting from version 12.60, the engine has been removed from TestComplete and replaced with a new OCR engine featuring Google Vision API.

If in your tests you use the deprecated OCR engine, you can do one of the following:

• Update your tests to use the new engine. See Migrate Tests Created in Earlier Versions.

• Continue using the deprecated engine (not recommended). To learn how to do it, please contact our Customer Care team.

• TestComplete versions prior to version 12.40 used the Layout name for controls of the com.android.internal.view.menu.ActionMenuView and android.widget.ActionMenuView classes. TestComplete version 12.4x and later use the Bar name for these classes. To avoid errors, you need to modify the tests created in TestComplete versions prior to 12.40.

  Possible Workarounds

  Possible WorkaroundsPossible Workarounds

  • Name Mapping. Remap the corresponding objects to update their identification criteria.

  • Default Naming. Modify the name of the corresponding objects, when you address them or their child objects. For example:

    • In TestComplete 12.31 and earlier:

      Mobile.Device("Nexus 4").Process("smartbear.example.orders").RootLayout("").Layout("action_bar_container").ActionBar("action_bar").Layout("NO_ID", 2).SearchView("action_search")

    • In TestComplete 12.40 and later:

      Mobile.Device("Nexus 4").Process("smartbear.example.orders").RootLayout("").Layout("action_bar_container").ActionBar("action_bar").Bar("NO_ID").SearchView("action_search")

• The table checkpoints you created for WPF ListView controls in TestComplete 12.42 and earlier are not compatible with the updated table checkpoints that TestComplete 12.50 introduces. So, if your legacy tests have table checkpoints created for WPF ListView controls, you need to update these checkpoints after migrating your test project to TestComplete 12.60.

• TestComplete 12 does not include the load testing plugin anymore. SmartBear offers a dedicated product for load testing – LoadComplete. You can learn more about it on our web site: http://smartbear.com/loadcomplete. For an overview of all load testing offerings, visit the SmartBear Load Test Solutions page.

  If you convert a load testing project created in TestComplete 7 or 8 to the new format:

  • The HTTP Load Testing item will become Unavailable in the Project Explorer.

  • The existing event handlers for the load testing events (OnLoadTestingRequest, OnLoadTestingResponse and others) will remain in the Events project item, but they will never be triggered.

• If your scripts use variables with the same names the scripting objects added in later TestComplete versions have, you need to rename the variables to avoid playback errors.

• TestComplete 12 uses the s namespace prefix instead of the SOAP prefix in SOAP requests to the tested web services. If your tests parse the result of the PrepareRequests method or the LastRequest property value, you may need to change the tests to use the new SOAP request structure. See an example of a new SOAP request.

• Test Visualizer settings are converted as follows:

  • In converted TestComplete 7 projects, Test Visualizer is disabled for test recording and for test runs.

  • In converted TestComplete 8 projects, disabled Test Visualizer remains disabled. Enabled Test Visualizer uses the Capture images option.

    For a description of the new options, see Default Project Properties - Visualizer Options.

• The TestComplete 12 project format differs significantly from the format used in TestComplete 6 and earlier versions. If you experience issues with converting or running your converted project, please contact SmartBear Support for help.

• In TestComplete 6 and earlier versions, you had to compile Delphi, C++Builder and Visual C++ applications with TestComplete libraries (tcOpenApp.pas, tcOpenAppClasses.pas, tcPublicInfo.pas and TCClient.cpp) to make them testable. This is no longer needed. To test your applications with TestComplete 12, recompile the applications without these libraries.

• TestComplete 12 uses a different SOAP namespace for web service testing (see above). You may need to update your tests to use the new namespace.