What's new in TestArchitect for Windows

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


TestArchitect Client

Enhancements to existing features
  • Import/Export command line tool:
  • 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).

TestArchitect Automation

Enhancements to existing features
  • Device Live Screen
    • Live mirroring: Device Live Screen (DLS) now allows your desktop monitor to mirror, in real time, the display of the selected device.
    • Two viewing modes
      • Fit-to-window mode: The DLS window’s display area is matched to the physical dimensions of the device under test.
      • Full screen mode: The DLS display is a one-to-one mapping of the monitor’s pixels with those of the device.
  • Improved Action Recorder for web apps on Internet Explorer:
    • New support for generation of actions:drag mouse, as well as media-based built-in actions, including pause, play, set media property, and set volume, are now written into test procedures by the recorder.
    • Highlight element on hover: While you are recording the test, as you move your pointer around the application, an orange, rectangular frame highlights whichever control the cursor is made to hover over, and displays the object's TA class, to assist you in deciding where to click.
    • Ignore formatting tags: The recorder determines whether to record the specific element that is interacted with, or to navigate up the DOM hierarchy until a suitable element is found. It then generates the appropriate built-in action with the recorder's choice of element specified as the control to be operated on.
  • 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.