TestArchitect Release Notes

TestArchitect 8.3 Update 5 Release Notes

Release Date: May 11, 2018

What's New in TestArchitect 8.3 Update 5

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

TestArchitect Client

New features

• Changing the TestArchitect command line's port. It not only resolves port conflict but also enable parallel test execution in Docker environment. By dedicating different ports to different command line interfaces, you can execute TestArchitect batch files on multiple containers residing within a single Docker host at once.

• Optimizing Java virtual machine parameters - MaxMetaspaceSize, MinHeapFreeRatio and MaxHeapFreeRatio (learn more) - for either TestArchitect performance or memory savings. These parameters, in general, control how garbage collection is performed by the Java HotSpot VM.

Enhancements to existing features

• Changing the test execution order: TestArchitect allows you to explicitly specify a custom execution order of test module invocations. For more comfort, the test execution order can be changed in the Execute Test dialog box or in a given static test suite.

• Previewing the summary of a checkpoint failure or an automation warning/error: You can quickly preview status of a checkpoint by selecting a specific checkpoint in the local/repository result list view and clicking its corresponding number of failures, warnings or errors. The first failure, warning or error of that checkpoint will be displayed in a tooltip.

• Additional integration support for Zephyr Enterprise Cloud version 6.1.

  • Importing Zephyr test cases into TestArchitect and Uploading TestArchitect test modules/tests cases to Zephyr: Test cases residing on Zephyr can be imported into TestArchitect. Likewise, TestArchitect test cases and test modules can be uploaded to Zephyr.

  • Execute test from Zephyr: As an alternative to executing tests from TestArchitect, TestArchitect test cases and test modules may be executed from Zephyr. Or Test cases and test modules can be executed in TestArchitect and their results are uploaded to Zephyr.

• Additional sections for the test result Summary tab, which reports basic test run information and summarizes various aspects of the test.

  • Known Bug Summary: Reviewing test results can assist you in determining if and when JIRA bug issues on a JIRA server should be closed.

  • Failure/Error Summary: This section displays all failure, error, or warning encountered during the test run.

  • Log Information: This section displays the logging information from the report actions, that is, report, report check, report warning, and report error in the test procedure.

• Recent Run Duration field supported in test module list views: This field shows the most recent execution time of a given test module.
  Note that, Recent Run Duration is available, when respective test results are added into the repository.

• Improvement for the Lab Manager: Host address is added to the Lab Manger. A host address is composed of the IP address and port number of the controller machine.

• Editing Source ID:A Source ID that is the ID of a test case in an external tool (Quality Center, Team Foundation Server or Zephyr) and is used for mapping purpose now can be modified quickly in a test case list view.

TestArchitect Automation

New features

• Additional support for Oracle Forms: TestArchitect supports testing of Oracle Forms. Now development and playback of tests for Oracle Forms applets are within your reach. It recognizes controls in Oracle Forms screens and provides specific built-in actions and properties for simulating user actions on these controls.
  • As of this release, Oracle Forms controls and timing built-in settings are supported by TestArchitect can be found at:
    • Support for timing built-in settings.
    • Support for Oracle Forms controls.
• New control flow built-in action provided:
  • continue: Skips the remaining action lines in the current iteration of a loop and proceeds to the next iteration.

Enhancements to existing features

• Support for new exit codes: These codes determine whether the overall final result status is Not Finished or not.
  • Possible values:
    • complete: The operation is successful.
    • incomplete: (Default) The operation is unsuccessful.
  • Affected built-in actions:
    • exit test case
    • exit test module
• exit loop built-in action, which terminates a loop immediately and moves to next action line following the loop, supports all types of TestArchitect loops, including:
  • while - end while
  • repeat - until
  • use data set - repeat for data set

Repository Server

Enhancements to existing features

• Primary-replication repositories configuration:
  • Registering replication repositories with the replica network by either hostname or IP:
    • IP address: IP address of your host machine. It should be used for registration when your replication machine has a static IP address.
    • Hostname: Name of your host machine. It should be used for registration when your machine has a dynamic IP address.
  • Breaking primary-replication relationship: A confirmation dialog appears to confirm if you really want to remove replication and/or primary repositories from the replica network.

Known Issues

• While testing web applications on Firefox and Chrome, which employ WebDriver, the ignore tabs and newline built-in setting do not affect the check table cell value built-in action.
• On local repository list view, the number of failed checkpoints and errors are displayed incorrectly.
• While mapping test case on test case list view, the source ID field is not locked and keeps the current value.

System Requirements

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

Additional Resources

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