Working with test results
TestArchitect automatically generates a report containing the results of an automated test after the test concludes. The test results are immediately displayed in the main window of TestArchitect Client.
- Less memory footprint: The amount of memory that TestArchitect uses or references while opening and viewing test results is less.
- Smaller parsing times: The operation process is faster, such as open test results, import/export test results, etc.
- Smaller test result compression: Test results take up less hard drive space; therefore, the repository’s size is reduced.
Colossal test results, which contain hundreds of thousands of action lines, might consume a huge amount of memory when they are open in a web browser. TestArchitect optimizes these test results by trimming a specific given number of iterations, and also removing the pagination page.
The number of truncated iterations is determined based on several predefined settings. Note that, these settings are adjustable. (Learn more.)
If you change the value of a user-defined field on the Information tab of a test module, it will not take effect on the test result of this test module. In other words, the test result will still adopt the default value set in the process of Creating a user-defined field.
Overview of test results
This topic contains information about various tabs and panels, and on viewing test results.
Converting test results generated in earlier versions to TestArchitect 8.3
It is required to convert test results created in versions prior to TestArchitect 8.3 into the new XML format. This topic explains how to convert test results and several important notes for test result conversion.
Customizing XML test results
In order to customize the layout of XML test results, you are required to edit XSLT style sheets.
Viewing latest test results
Viewing the local result details of the most recently executed test.
Adding test results to the repository
Test results reside locally, in the LOCAL RESULTS node, until they are either deleted or explicitly added to the repository.
Exporting test results
Test run results stored on the local machine or in the repository can be converted and exported to .TARESULT, HTML, XML, and xUnit.
Importing test results from ZIP file
TestArchitect lets you easily import a repository test result archive file (.ZIP format).
Importing test results from .TARESULT files
TestArchitect lets you easily import a test result archive file (.TARESULT format).
Comparing test results
Comparing the results of two test runs is useful in tracking and debugging new and existing issues in the AUT.
Opening latest test result
Opening the most recent result, for a test run multiple times.
Opening baseline result
If your test module contains a baseline test result, you can conveniently open that result.
Receiving test results of remote test execution
TestArchitect allows you to execute a test remotely and receive the test results from the remote machine, although TestArchitect Client is closed on the local machine, even before the remote execution is complete.
Displaying test results in a browser
TestArchitect test results may be opened in a web browser on any machine. TestArchitect need not be installed to view the results.
Distributed result storage
You can store test results across multiple locations as an alternative to a centralized repository in TestArchitect Client.
Comparing test results