Native reporters for WebdriverIO and Appium
New Qualflare reporters for WebdriverIO and Appium record every retry attempt, screenshots tied to each attempt, and the browser or device each test ran on.
Qualflare now has native reporters for WebdriverIO and for Appium suites run through WebdriverIO. They record what JUnit output can't: each retry attempt with its own error, the screenshots taken during it, and the exact browser or device the test ran on.
What's new
- Every attempt, separately. With Mocha retries, each attempt keeps its own error, start time and duration. A test that passed on a retry is marked flaky.
- Screenshots in the right place. Screenshots you take, whole-page or of an element, are attached to the test and the attempt that took them, including ones from
afterTesthooks. - Browser and device details. Platform (web, iOS, Android or desktop), device, OS version, browser and browser version are recorded for each test. Chrome and Firefox runs keep separate histories.
- Steps and metadata. Add nested steps, labels, links, tags and priority from your tests with
qualflare.*helpers. - WebdriverIO and Appium test types. Launches show as WebdriverIO or Appium in Qualflare, each with its own icon.
How to use it
npm install --save-dev @qualflare/webdriverio # or @qualflare/appium
Add ['@qualflare/webdriverio', { environment: 'staging' }] (or @qualflare/appium) to reporters in your WebdriverIO config, run your tests, then upload the results:
qf my-project collect ./qualflare-results
Availability
Requires WebdriverIO 8 or 9, and qf 0.1.37 or newer so launches are labeled correctly. Cucumber with WebdriverIO isn't supported yet. For Appium suites written in Java or Python, use the TestNG, JUnit 5 or pytest reporters.