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 Jubula 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.
Copyright BREDEX GmbH 2013. Made available under the Eclipse Public License v1.0.