Apptim gives users the ability to create custom marks while running a test, in two different ways:
- Single Marks: A graphical identification of single time marks in test results timeline (charts and videos).
- Time taken: Measuring different event duration times during a test (using START | STOP flags)
How to enable Apptim Marks?
Users can take advantage of this functionality by adding a single line of code in their Android app's code.
Single Mark (timestamp)
Add a log entry when the event happens:
Log.i("{APPTIM_EVENT}", "event-name")Time taken per Event
Add a log entry on both, at the beginning and the end of an event:
Log.i("{APPTIM_EVENT}:", "event-name, START") ... Log.i("{APPTIM_EVENT}:", "event-name, STOP")Considerations
Precision (ms)
All marks will be stored with milliseconds precision and relative to the test session start time.
Event naming
Event names can be any string without comma ,
Duplicate events in time-taken
When using START | STOP marks, Apptim will assume that the first STOP corresponds with the first START of the same event-name to have a deterministic way of correlation.
For example, if the event sequence is the following:
Log.i("{APPTIM_EVENT}:", "Event A, START") // A1 sleep (10 ms) Log.i("{APPTIM_EVENT}:", "Event A, START") // A2 sleep (20 ms) Log.i("{APPTIM_EVENT}:", "Event A, STOP") // A1 sleep (30 ms) Log.i("{APPTIM_EVENT}:", "Event A, STOP") // A2Apptim will assume that the first STOP corresponds with the first START of the same event-name, resulting in:
- Event A(1) time taken: 30 ms
- Event A(2) time taken: 50 ms
📒 To avoid this confusion you can always add ID's on event names.
Logs
All Apptim Marks can be found at events.tsv file inside Logs section.
Support
If you have any questions on how to enable and use Apptim Marks, please contact our team at [email protected] and we'll help you get started.