TestArchitect Release Notes

TestArchitect 8.3 Update 2 Release Notes

Release Date: August 31, 2017

Download PDF for OSX
Download PDF for Linux
  • Please note
  • 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.

What's New in TestArchitect 8.3 Update 2

The following new features and improvements are introduced in the latest version of TestArchitect running under Windows.

TestArchitect Client

New features

  1. Modern TestArchitect command-line interface:
    • Flexibility: With new TestArchitect's command line tool, tests can be launched from a command shell. When incorporated into batch files, the tool significantly extends the flexibility of test execution, especially from a scheduling standpoint.
    • Standards for command-line interfaces: In order to provide a consistent, cohesive user experience, the new TestArchitect command-line interface has been standardized on the following aspects:
      • Consistent argument naming conventions
      • Consistent error messages and exit codes
      • Consistent command syntax
    • Ease of use: The presence of optional arguments in batches files is no longer required. When the optional arguments are absent, their default value will be automatically applied.
  2. A separate TestArchitect Help package: The TestArchitect Help package has been removed from TestArchitect installer. If you'd like to continue to open local help documentation in offline mode, please follow this link.

Enhancements to existing features

  • Improved TestArchitect-Team Foundation Server integration:
  • Adding test results to the repository:
    • In the CI/CD process, after automated tests are entirety finished, you are able to automatically add local test results into the repository, even if the specified result folder might not exist beforehand.
    • At the moment, TestArchitect is capable of dynamically creating result folders on-the-fly. Name of the result folders is determined based on the following predefined macro variables.
Macro variables Description Output (example)
{year}Gets the current year2017
{month}Gets the current month08
{day}Get the current date09
{today}Get today's date in the form of mm-dd-yyyy08-09-2017

  • Exporting test results into various formats:
    • Export results into .TARESULT format:
      • Test run results now can be converted and exported to .TARESULT, an archive filename extension developed by LogiGear. This new extension is extremely convenient for test result query purposes, especially in the CI/CD process. Specifically, upon test completion, you can aggregate all test results quickly by just simply querying all returned .TARESULT files.
      • TARESULT then also can be imported back into TestArchitect.
    • Export results into HTML format:
      • XSLT template: Ability to export HTML results with your own view layout, customized by your XSLT template.
      • Directory structure output: Ability to output different types of directory structure folder which store HTML files.
        • Folder structure: TestArchitect creates a hierarchical tree structure, or subdirectories to store HTML results.
        • Flat structure: TestArchitect does not create subdirectories. There is only a single top-level directory which contains all HTML results.
      • Create output folders on-the-fly: TestArchitect automatically creates a folder to store HTML files if the specified folder does not exist.
  • TAUtilities, a library which allows you to connect and retrieve data from a TestArchitect repository server, is updated:
    • Result interface:
      • getIgnoredFails(): Returns the number of failed checkpoints that are marked as known bugs.
    • Project interface: Additional filename extension (.TARESULT) supported for the following methods:
      • exportFromPath(): Export a specific project item, identified by its TA path, to a file.
      • exportFromId(): Export a specific project item, identified by its TestArchitect ID, to a file.

TestArchitect Automation

New features

  • Testing in cloud services:
    • Official release for automation testing in WebDriver based cloud services: It delivers cost saving, time saving, remote/mobile access to information, high productivity, and increased test coverage across different mobile device types, etc.
    • Execution on multiple cloud devices: You are now able to automate tests on multiple cloud devices concurrently. The cloud devices will be defined via desired capabilities, specified in JSON files
    • New built-in disconnect all cloud devices action added: Logically disconnect all currently-connected cloud devices.
    • web element matching built-in setting: Specify which technique is used to perform web UI element matching.
  • Web service testing:
    • New built-in actions supported:
      • configure web service settings: Send JSON string request to a web service in order to apply new configuration settings.
        • Proxy: Defines a manual proxy server.
        • SSL: Defines SSL configurations.
        • Cookies: Specifies HTTP cookies that are sent back to the server.
        • Encoder: Specifies configurations for the encoder.
        • Decoder: Specifies configurations for the decoder.
        • Redirect: Configures the redirect settings
      • attach file: Attach given file(s) to a web service.
    • Common HTTP request methods are fully supported for the send http request action including:
      • GET: Request data from a specified resource.
      • POST: Submit data to be processed to a specified resource.
      • PUT: Replace all the current representations of the target resource with the uploaded content.
      • DELETE: Remove all the current representations of the target resource given by URI.
      • PATCH: The PATCH method is used to apply partial modifications to a resource.
      • HEAD: The HEAD method asks for a response identical to that of a GET request, but without the response body.
      • OPTIONS: The OPTIONS method is used to describe the communication options for the target resource.
  • A new method of AbtEntity for a user-scripted action (applicable to Java and C# harnesses only):
    • ExecuteScript: Executes JavaScript code of a specified web page, or inline JavaScript.

Enhancements to existing features

  • Android testing:
    • Support for Android 7.0: You can now run tests for applications on Android devices
  • iOS testing:
    • Support for iOS 10.3.2: You can now run tests for applications on iOS devices running this iOS version.
  • Web testing:
    • Added support for Firefox 54: Now you can create and run automated tests for web pages that are displayed in this version of Firefox.

Known Issues

  • On Android 7, occasionally the enter built-in action enters an incorrect value into a given control.

System Requirements

The following table lists the recommended hardware and software requirements for TestArchitect.

Recommended system requirements

TestArchitect Client/Controller with small-scaleRepository Server Production-scale Repository Server(up to 15 concurrent connections,1GB repository)
Operating systemWindows 7 or newer (Learn more)Windows 2008/2012 Server
HDDAt least 2.5GB available spaceAvailable space of at least 2 GB plus total aggregate size of all databases
CPU2 GHz dual-core or faster3.1 GHz quad-core

Additional Resources

For more information, please visit our website at www.testarchitect.com or email us at [email protected].

Copyright © 2024 LogiGear Corporation. All rights reserved. LogiGear is a registered trademark, and Action Based Testing and TestArchitect are trademarks of LogiGear Corporation. All other trademarks contained herein are the property of their respective owners.


1730 S. Amphlett Blvd. Suite 200, San Mateo, CA 94402

Tel +1 (650) 572-1400