You can configure your AUT to run with Chronon recording so that you can analyze any errors that occur during your automated test runs. See the section later (Section 3.36.2.4, “Analyzing the generated reports”) on analysing the reports for information on the tooling required to do this.
![]() |
Jubula Feature users: The support for Chronon recording in AUTs is currently only available in the standalone software. |
You can select Chronon as a monitoring agent and configure it in the Expert Settings in the AUT configuration.
Open the AUT configuration dialog from the Project properties (Section 3.6.3, “Editing the Project and AUT properties”).
Select the Expert configuration.
Select Chronon (separate installation) as a monitoring agent (Section 3.36.2.2, “Configuring the separate Chronon installation for use with your AUT”).
You can then enter the configuration details for the monitoring.
Enter the following configuration details:
Enter the path to the Chronon recorder JAR you have installed.
The path to the platform-specific native recorder agent library.
Enter the absolute path to the configuration file for the recorder. The configuration file has the same setup as a Java properties file. It must contain the following properties:
servermode (set to true)
name (the AUT name as it will be displayed in the Chronon Recording Server UI)
autostartwithconfig (if you want the recording to start automatically (recommended) then the recording parameters need to be set in the Chronon application.)
port (optional – if none is entered, 8042 is used.).
The documentation for the configuration file is available on the Chronon site:
http://chronon.onconfluence.com/ display/DOC/Recorder+Configuration+File
![]() |
You can also refer to the Chronon documentation for information on the required parameters to run your tests with the Recording Server. : http://chronon.onconfluence.com /display/DOC/Recording+outside+Eclipse |
You should bear the following in mind when using Chronon for recording information in automated tests.
Performance in the AUT may be affected
The recordings that Chronon performs are very memory-intensive. For this reason, you may notice performance differences in your AUT. It may also be necessary to increase the step delay for your tests, and / or add extra synchronization to compensate for the performance differences when Chronon is running.
For these reasons, we do not recommend having Chronon configured as a part of your standard AUT configuration. Instead, we suggest running tests with Chronon monitoring when needed.
We also strongly suggest ensuring that your AUT and the machine it is running on have sufficient memory to cope with the increased monitoring activity.
Stopping or restarting the AUT will cause the previously recorded information to be lost
The recording files are written when the AUT is stopped. This means either stopping the AUT by hand, using the ”Stop AUT” button in on the toolbar in the ITE or when you use the restart action.
Because of this, we recommend executing individual Test Cases (use cases) in Test Suites that you want to analyze with Chronon. You should ensure that any Event Handlers in the Test Suite will not cause the AUT to restart.
To analyze the reports generated, you will require the Chronon Time Travelling Debugger from Chronon Systems. You can download a trial version of this tool. The link to the trial version is provided in the expert AUT configuration.
Open source projects may contact Chronon Systems for free licenses.