-
Notifications
You must be signed in to change notification settings - Fork 28
Reports
Emcee might produce various types of reports. Basic knowledge of test run status you can find in client log. Other reports should be specified explicitly, below is an exhausting list for iOS. It's allowed to use any combination of reports in test run.
Android reports might be found in android doc.
Use with --result-bundle result.xcresult argument.
Emcee will collect partial xcresults from workers and merge it to single directory that may be opened in XCode. Host where client gets run should be accessible by workers.
Use with --allure-report allure-report argument.
Emcee will build allure report based on xcresult including snapshots and video artifacts. Allure report might be rendered in browser with allure tool.
Use with --junit junit-report.xml argument.
Emcee will create single junit report for all test destinations (if many).
Use with --emcee-result-json emcee-report.json argument.
Emcee will produce a report with proprietary format that consists of successful/failed/skipped tests enriched with metainformation such as duration, logs, hostname and simulator where test was executed.
Use with --trace trace-report argument.
Emcee will generate per-bucket trace file that can be loaded into chrome://tracing. Use it to get insights when making decisions on equipment purchase or problem investigation.