Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/appium/appium-event-parser
Node CLI script to help parse event timing output from Appium scripts
https://github.com/appium/appium-event-parser
Last synced: 1 day ago
JSON representation
Node CLI script to help parse event timing output from Appium scripts
- Host: GitHub
- URL: https://github.com/appium/appium-event-parser
- Owner: appium
- Created: 2017-03-15T19:55:07.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2019-11-06T00:34:46.000Z (about 5 years ago)
- Last Synced: 2024-08-02T20:44:36.876Z (3 months ago)
- Language: JavaScript
- Size: 8.79 KB
- Stars: 4
- Watchers: 7
- Forks: 3
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
appium-event-parser
===========
This is a simple CLI script to parse Appium event timings. What are event timings? When you pass the capability `eventTimings` with the value `true` to an Appium session, then when calling the get session capabilities command in your client (`GET /session/:id`) you will have an `events` key in the response object. This key contains information about Appium-internal events and when they occurred. This information is useful for profiling Appium or debugging Appium, and is not generally useful for users.
Any custom data added to the event timing JSON (for instance, to identify a build) can be marked with a property `iterate` set to `false`.
## Installation
```
npm install -g appium-event-parser
```
## Requirements
* NodeJS v7+
## Usage
First of all you need to have the output from `GET /session/:id` stored in a `.json` file somewhere. The best time to call `GET /session/:id` is right before calling `driver.quit()` so that you know you've received all the events you might care about.
### Timeline
You can build a timeline of the events from this session using `-t`:
```
appium-event-parser -t -i /path/too/response.json
```
Which will show something like:
```
[xcodeDetailsRetrieved@0s]
[[email protected], [email protected], [email protected], [email protected]]
|
|
|
|
|
(32.126s)
|
|
|
|
|
|
[[email protected]]
(5.033s)
[[email protected], [email protected]]
|
|
|
|
|
|
|
|
|
|
(58.28s)
|
|
|
|
|
|
|
|
|
|
|
[[email protected]]
|
(10.725s)
|
|
[[email protected]]
|
(11.949s)
|
|
[[email protected]]
[[email protected], [email protected], [email protected], [email protected]]
```
You can adjust the number of lines taken up by the timeline with the `-l` parameter (e.g., `-l 50` is the default of 50 lines).
### Comparison statistics
If you have a directory with lots of session capabilities `.json` files, you can get stastical information about certain events we care about in the XCUITest driver:
```
appium-event-parser -s -i /path/to/dir/with/jsons
```
And you'll get something like:
```
{ avgs:
{ simStartLength: 41.5121,
wdaStartLength: 17.941200000000002,
wdaSessionStartLength: 2.0113000000000003,
numWdaStartAttempts: 1,
numWdaSessionAttempts: 1 },
stdevs:
{ simStartLength: 2.4527162269614475,
wdaStartLength: 2.4414009420822302,
wdaSessionStartLength: 0.13611102086164817,
numWdaStartAttempts: 0,
numWdaSessionAttempts: 0 } }
```
That's about it!