What's new in TestArchitect for Linux

The following new features and improvements are introduced in TestArchitect version 8.2 Update 1 running under Linux.

Remember:

Before upgrading to the latest version of TestArchitect, it is strongly recommended that you back up all repositories.
A TestArchitect client and any repository server to which it connects must be of the same version.

TestArchitect Client

Startup settings: The new Startup Settings panel on the Execute Test dialog box provides a means by which you can specify settings prior to a test run. For example, you can choose the browser in which to run a test by specifying a value for setting use browser without using variations. Or you can specify a user-defined setting such as test environment, then in turn retrieve its specified value within your tests using the action get setting.

Enhancements to existing features

Repository results can be exported to HTML.
Open/copy/cut/drag multiple items from list view to tree view: Drag and drop any project item, or a selection of items, from a list view into a folder or node of the same type in the TestArchitect explorer tree. Alternatively, cut or copy items from a list view and paste into TestArchitect explorer tree. It is also now possible to open multiple items at one time from a list view.
Support for repository name and project name parameters in test run batch file: New parameters /dbname and /proname, which take precedence over /srvid (repository ID) and /proid (project ID).

Properties Comparison: A new feature of the TestArchitect Interface Viewer, Property Comparison allows you to compare and contrast the property values of your interface definitions with those of their “physical” counterparts (controls, windows, etc.) in the tested application. This is especially helpful when, perhaps due to an application update, a given interface definition can no longer identify the application’s UI object that it was originally matched with.
Read user-defined and built-in settings in your test procedures and user-scripted actions: The built-in action get setting, expression function #getsetting, and AbtLibrary class method GetSetting() are provided to read settings into variables.
Engine class method exposed, getEntityInformation() (AbtLibrary): This method retrieves the metadata of a TestArchitect entity, such as a test module, data set, or user-defined action, for use within your user-scripted actions. Retrieved information includes name, location, status, recent result, url, assigned user, priority, and version.

Enhancements to existing features

get tree node menu state and check tree node menu state actions: optional arguments x and y are provided to determine horizontal and vertical positions of the effective click on a specified tree node.