Performance tracing is a useful feature for optimizing your test execution times. It collects detailed information about the time it takes events like repository item searches or mouse input actions to happen during a test run. It collects this information in a log that you can then view and organize with Excel, for example.
In this and the following chapters, find out how to enable performance tracing, what the individual tracers collect, what the log files look like, and finally, some recommendations from us to get the most out of this feature.
Enable performance tracing
Performance tracing is disabled by default. When enabled, it applies to all test runs until you disable it again.
To enable it:
-
With a solution opened, go to Settings > Plugins > Performance tracing.
-
Under Active tracer, select a tracer (for descriptions see further below).
-
(optional) Change the default output directory for the generated trace logs. The default is %MyDocuments%RanorexTraceLogs.
Tracers
There are 6 predefined tracers available. They allow you to customize what information you want to collect.
-
None: Performance tracing is disabled. No information will be collected.
-
Repository: Collects information about searched repository items (search time, RanoreXPath, search attempts, etc.)
-
MouseInput: Collects information about mouse actions only (linked repository item, execution time, etc.). This applies to the following mouse actions: Move, Click
-
KeyboardInput: Collects information about keyboard actions only (linked repository item, execution time, etc.). Applies to the following keyboard actions: Key sequence, Key shortcut press
-
AllInput: Combines the MouseInput and KeyboardInput tracers.
-
Misc: Collects information about miscellaneous actions and processes, like fixed delays, tracing screenshots, and Run/Close application actions.
-
All: Combines all of the other tracers. Collects the information in a more concise format.