The following new features and improvements are introduced in the latest version of TestArchitect 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 of the same version.
- Modern TestArchitect
- 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
- 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
- A separate TestArchitect Help
file installer: 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
- Adding test results to the repository:
- In the Continuous Integration/Continuous Deployment (CI/CD) process, after
automated tests are entirety finished, you are able to 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.
||Gets the current year
||Gets the current month
||Get the current date
||Get today's date in the form of mm-dd-yyyy
- Exporting test results into
- Export test result into .TARESULT files:
- Test run results now can be converted and exported to
.TARESULT extension, 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 test results to HTML:
- 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
- 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
- Create output folders on-the-fly: TestArchitect automatically creates a folder to
store HTML files if the specified folder does not exist.
- Support for Red Hat Enterprise Linux 6.6 and 7.2: Now, you can run your tests
under Red Hat Enterprise Linux 6.6 and 7.2 to check whether your application works
correctly with this version of the Linux operating system.
- Web service
- New built-in actions supported:
- configure web
service settings: Send JSON string request to a web service in order to apply new
- Proxy: Defines a manual proxy server.
- SSL: Defines SSL configurations.
- Cookies: Specifies HTTP cookies that are sent back to the
- 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
- GET: Request data from a
- 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):
Enhancements to existing features