The following new features and improvements are introduced in the latest version of TestArchitect running on Windows.
- 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.
- Standardized TestArchitect
test result status:
- Current result statuses, including Passed,
Failed, Passed with
Warnings/Errors, Passed with Known
Bugs, and Not Run, are refined in such
a way that the conditions and interpretations are consistent and are administered in
a standard manner. This limits false positive and false negative errors that might
occur in test results.
- Adding a new result status, Not
Finished: Reviewing test results is easier, because this
new status helps you distinguish the cases in which a test is started, but it is
unable to reach the end of an automated run.
Please note that, the number of
automation errors/warnings, and passed/failed checkpoints do not matter in this
- Automation runs that crash unexpectedly are Not
- Automation errors occur and they are handled by the following built-in
Enhancements to existing features
repositions: Default value of data synchronization mode between the primary repository and the replication
repository is changed from Lazy to Eager, which means
that the data by default is synchronized immediately after each modification.
- Improved TestArchitect-Team Foundation Server (TA-TFS)
- Support for uploading TestArchitect test results to TFS as an HTML file
attachment with customized HTML view layout in the following functionalities.
- New GUI for the TestArchitect
Execution dialog box, used to invoke TestArchitect tests
from external test management tools.
- Export test results to various output formats:
- XML detail: Exports test results to XML file once the test
execution is complete.
- xUnit: Exports test results to a XML file in xUnit-format for
integrating into the continuous
integration tools once the text execution is complete.
- HTML: Export test results to HTML file automatically once the text
execution is complete
- o Added TA-TFS plug-in’s
- Easier to associate test
- Ability to disassociate test
- Filtering test cases while test association and
disassociation: By defining query fields, operators, and macros (learn more), you can filter in work
items to return the set of work items that interest you.
- TA-TFS Extensibility:
Additional constants are provided to support the following features while
uploading TestArchitect test results to TFS.
- Exporting TestArchitect test results into various formats including
XML, and xUnit to a specified
- Running automated tests on physical or cloud mobile devices.
- Configuring automation playback tools.
- Using TFS test ID to name the TestArchitect test results attached
- Testing with Oracle: TestArchitect supports working with Oracle database and
allows both reading data from and writing it to databases. You can connect to the needed
database directly from your test and specify parameters that are used to get access to
- Supported Oracle Database product family:
- Oracle Database Enterprise Edition
- 12c Release 2
- 11g Release 2
- Oracle Database Express Edition
- Added Beta support for replacing the anchor and/or anchor pos properties by the XPath property: In order
to leverage the power of XPath in web automation testing, you can quickly convert
previously-captured anchor and/or anchor pos
by applying the anchor pos
report built-in setting.
- Support for automation on modal dialog boxes in Internet
Explorer: TestArchitect supports modal dialogs that
display other web templates. Specifically, TestArchitect
detects these dialogs in the Internet Explorer web browser and allows you to automate
them as part of your tests.
Enhancements to existing features
- Web services testing
- Amazon Web
Services (AWS) support: TestArchitect allows you to run automated tests on AWS
which enables you to remove hardware-based resource constraints to quickly create
developer environments and expand your testing machine fleet.
When you send HTTP requests to AWS, you are required to sign the requests so that
AWS can identify who sent them. To sign a request, you first need to calculate
- As of this release, signing process is not yet supported through TestArchitect's built-in actions. Consequently,
you need to program a user-scripted
action for the signing process (refer to the below links).
- If you face difficulties while creating a signature, please
contact TestArchitect Support at email@example.com
- A new parameter for the Encoder
- addDefaultContentCharsetToContentType: Tells
whether REST Assured should automatically append the content
charset to the content-type header if
content charset is not defined explicitly.
- Support for HTTP digest authentication: TestArchitect
provides you with additional approach for specifying web service credentials which
is Digest Authentication. To work with web services that require Digest
authentication, use the authenticate built-in action.
- Support for writing responses to a file in TestArchitect: You are able to save binary data
files embedded in the given web service's HTTP response. The response
file argument of send http request specifies a filename and an
extension of the stored file.
- Improved exec script and added new support for ExecuteJS to retrieve the
- Support for the Firefox updates: You can play back tests for web applications running in the following versions of the
Firefox web browser: 55 and 56.