{"id":13612795,"url":"https://github.com/appium/appium-event-parser","last_synced_at":"2025-07-01T06:35:24.907Z","repository":{"id":66331856,"uuid":"85115100","full_name":"appium/appium-event-parser","owner":"appium","description":"Node CLI script to help parse event timing output from Appium scripts","archived":false,"fork":false,"pushed_at":"2019-11-06T00:34:46.000Z","size":9,"stargazers_count":5,"open_issues_count":3,"forks_count":3,"subscribers_count":6,"default_branch":"master","last_synced_at":"2025-06-10T13:09:31.903Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"JavaScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/appium.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null}},"created_at":"2017-03-15T19:55:07.000Z","updated_at":"2025-04-05T21:51:30.000Z","dependencies_parsed_at":"2023-02-20T19:45:48.610Z","dependency_job_id":null,"html_url":"https://github.com/appium/appium-event-parser","commit_stats":null,"previous_names":[],"tags_count":4,"template":false,"template_full_name":null,"purl":"pkg:github/appium/appium-event-parser","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/appium%2Fappium-event-parser","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/appium%2Fappium-event-parser/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/appium%2Fappium-event-parser/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/appium%2Fappium-event-parser/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/appium","download_url":"https://codeload.github.com/appium/appium-event-parser/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/appium%2Fappium-event-parser/sbom","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":262914208,"owners_count":23383846,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-08-01T20:00:34.601Z","updated_at":"2025-07-01T06:35:24.885Z","avatar_url":"https://github.com/appium.png","language":"JavaScript","funding_links":[],"categories":["HarmonyOS"],"sub_categories":["Windows Manager"],"readme":"appium-event-parser\n===========\n\nThis 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.\n\nAny custom data added to the event timing JSON (for instance, to identify a build) can be marked with a property `iterate` set to `false`.\n\n## Installation\n\n```\nnpm install -g appium-event-parser\n```\n\n## Requirements\n\n* NodeJS v7+\n\n## Usage\n\nFirst 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.\n\n### Timeline\n\nYou can build a timeline of the events from this session using `-t`:\n\n```\nappium-event-parser -t -i /path/too/response.json\n```\n\nWhich will show something like:\n\n```\n [xcodeDetailsRetrieved@0s]\n [appConfigured@0.951s, resetStarted@0.958s, resetComplete@0.959s, logCaptureStarted@1.06s]\n |\n |\n |\n |\n |\n (32.126s)\n |\n |\n |\n |\n |\n |\n [simStarted@33.186s]\n (5.033s)\n [appInstalled@38.219s, wdaStartAttempted@38.239s]\n |\n |\n |\n |\n |\n |\n |\n |\n |\n |\n (58.28s)\n |\n |\n |\n |\n |\n |\n |\n |\n |\n |\n |\n [wdaStartFailed@96.519s]\n |\n (10.725s)\n |\n |\n [wdaStartAttempted@107.244s]\n |\n (11.949s)\n |\n |\n [wdaSessionAttempted@119.193s]\n[wdaSessionStarted@123.705s, wdaPermsAdjusted@123.746s, wdaStarted@123.747s, orientationSet@124.146s]\n```\n\nYou 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).\n\n### Comparison statistics\n\nIf 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:\n\n```\nappium-event-parser -s -i /path/to/dir/with/jsons\n```\n\nAnd you'll get something like:\n\n```\n{ avgs:\n { simStartLength: 41.5121,\n wdaStartLength: 17.941200000000002,\n wdaSessionStartLength: 2.0113000000000003,\n numWdaStartAttempts: 1,\n numWdaSessionAttempts: 1 },\n stdevs:\n { simStartLength: 2.4527162269614475,\n wdaStartLength: 2.4414009420822302,\n wdaSessionStartLength: 0.13611102086164817,\n numWdaStartAttempts: 0,\n numWdaSessionAttempts: 0 } }\n```\n\nThat's about it!\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fappium%2Fappium-event-parser","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fappium%2Fappium-event-parser","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fappium%2Fappium-event-parser/lists"}