The following new features and improvements are introduced in the latest version of TestArchitect running on macOS.
- 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
- 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.