User Guide Version history Features added to TestArchitect 8.3 Update 5

 What's new in TestArchitect for Linux

What's new in TestArchitect for Linux

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

• 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 the same version.

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 list view.
• 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 views 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 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: Displaying all failure, error, or warning encountered during the test run.
  • Log Information: Displaying 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. The field 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.
• Generating batch file to run on separate terminals: Activating this option forces your batch files to run on multiple terminals in a parallel manner.

TestArchitect Automation

New features

• New control flow built-in action provided:
  • continue built-in action: 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: Determines 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, which terminates a loop immediately and moves to next action line following the loop, is capable of supporting 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.