Back to Webdriverio

Test Output

website/docs/visual-testing/test-output.md

9.28.08.7 KB
Original Source

:::info

This WebdriverIO demo site has been used for the example image output.

:::

enableLayoutTesting

This can be set on the Service Options as well as on the Method level.

js
// wdio.conf.(js|ts)
export const config = {
    // ...
    // =====
    // Setup
    // =====
    services: [
        [
            'visual',
            {
                enableLayoutTesting: true
            }
        ]
    ]
    // ...
}

The image output for the Service Options is equal to the Method, see below.

Image Output

<Tabs defaultValue="saveelement" values={[ {label: 'saveElement | checkElement', value: 'saveelement'}, {label: 'saveScreen | checkScreen', value: 'savescreen'}, {label: 'saveFullPageScreen | checkFullPageScreen', value: 'savefullpagescreen'}, {label: 'saveTabbablePage | checkTabbablePage', value: 'saveTabbablePage'}, ]}

<TabItem value="saveelement">
js
await browser.saveElement(".features_vqN4", "example-element-tag", {enableLayoutTesting: true})
// Or
await browser.checkElement(".features_vqN4", "example-element-tag", {enableLayoutTesting: true})

</TabItem> <TabItem value="savescreen">
js
await browser.saveScreen("example-page-tag")

</TabItem> <TabItem value="savefullpagescreen">
js
await browser.saveFullPageScreen("full-page-tag")
// Or
await browser.checkFullPageScreen("full-page-tag", {enableLayoutTesting: true})

</TabItem> <TabItem value="saveTabbablePage">
js
await browser.saveTabbablePage("tabbable-page-tag")
// Or
await browser.checkTabbablePage("tabbable-page-tag", {enableLayoutTesting: true})

</TabItem> </Tabs>

save(Screen/Element/FullPageScreen)

Console Output

The save(Screen/Element/FullPageScreen) methods will provide the following information after the method has been executed:

js
const saveResult = await browser.saveFullPageScreen({ ... })
console.log(saveResults)
/**
 * {
 *   // The device pixel ratio of the instance that has run
 *   devicePixelRatio: 1,
 *   // The formatted filename, this depends on the options `formatImageName`
 *   fileName: "examplePage-chrome-latest-1366x768.png",
 *   // The path where the actual screenshot file can be found
 *   path: "/path/to/project/.tmp/actual/desktop_chrome",
 * };
 */

Image Output

<Tabs defaultValue="saveelement" values={[ {label: 'saveElement', value: 'saveelement'}, {label: 'saveScreen', value: 'savescreen'}, {label: 'saveFullPageScreen', value: 'savefullpagescreen'}, ]}

<TabItem value="saveelement">
js
await browser.saveElement(".hero__title-logo", "example-element-tag")

<Tabs defaultValue="desktop" values={[ {label: 'Desktop', value: 'desktop'}, {label: 'Android', value: 'android'}, {label: 'iOS', value: 'ios'}, ]}

<TabItem value="desktop"> ![saveElement Desktop](/img/visual/wdioLogo-chrome-latest-1-1366x768.png) </TabItem> <TabItem value="android"> ![saveElement Mobile Android](/img/visual/wdioLogo-EmulatorAndroidGoogleAPIPortraitNativeWebScreenshot14.0-384x640.png) </TabItem> <TabItem value="ios"> ![saveElement Mobile iOS](/img/visual/wdioLogo-Iphone12Portrait16-390x844.png) </TabItem> </Tabs> </TabItem> <TabItem value="savescreen">
js
await browser.saveScreen("example-page-tag")

<Tabs defaultValue="desktop" values={[ {label: 'Desktop', value: 'desktop'}, {label: 'Android ChromeDriver', value: 'android-chromedriver'}, {label: 'Android nativeWebScreenshot', value: 'android-native'}, {label: 'iOS', value: 'ios'}, ]}

<TabItem value="desktop"> ![saveScreen Desktop](/img/visual/examplePage-chrome-latest-1366x768.png) </TabItem> <TabItem value="android-chromedriver"> ![saveScreen Mobile Android ChromeDriver](/img/visual/screenshot-EmulatorAndroidGoogleAPIPortraitChromeDriver14.0-384x640.png) </TabItem> <TabItem value="android-native"> ![saveScreen Mobile Android nativeWebScreenshot](/img/visual/screenshot-EmulatorAndroidGoogleAPIPortraitNativeWebScreenshot14.0-384x640.png) </TabItem> <TabItem value="ios">

:::info TIP iOS saveScreen executions are by default not with the device bezel corners. To have this please add the addIOSBezelCorners:true option when instantiating the service, see this :::

</TabItem> </Tabs> </TabItem>

<TabItem value="savefullpagescreen">
js
await browser.saveFullPageScreen("full-page-tag")

<Tabs defaultValue="desktop" values={[ {label: 'Desktop', value: 'desktop'}, {label: 'Android', value: 'android'}, {label: 'iOS', value: 'ios'}, ]}

<TabItem value="desktop"> ![saveFullPageScreens Desktop](/img/visual/fullPage-chrome-latest-1366x768.png) </TabItem> <TabItem value="android"> ![saveFullPageScreens Mobile Android](/img/visual/fullPage-EmulatorAndroidGoogleAPIPortraitChromeDriver14.0-384x640.png) </TabItem> <TabItem value="ios"> ![saveFullPageScreens Mobile iOS](/img/visual/fullPage-Iphone12Portrait16-390x844.png) </TabItem> </Tabs> </TabItem> </Tabs>

check(Screen/Element/FullPageScreen)

Console Output

By default, the check(Screen/Element/FullPageScreen) methods will only provide a mismatch percentage like 1.23, but when the plugin has the option returnAllCompareData: true the following information is provided after the method has been executed:

js
const checkResult = await browser.checkFullPageScreen({ ... })
console.log(checkResult)
/**
 * {
 *     // The formatted filename, this depends on the options `formatImageName`
 *     fileName: "examplePage-chrome-headless-latest-1366x768.png",
 *     folders: {
 *         // The actual folder and the file name
 *         actual: "/path/to/project/.tmp/actual/desktop_chrome/examplePage-chrome-headless-latest-1366x768.png",
 *         // The baseline folder and the file name
 *         baseline:
 *             "/path/to/project/localBaseline/desktop_chrome/examplePage-chrome-headless-latest-1366x768.png",
 *         // This following folder is optional and only if there is a mismatch
 *         // The folder that holds the diffs and the file name
 *         diff: "/path/to/project/.tmp/diff/desktop_chrome/examplePage-chrome-headless-latest-1366x768.png",
 *     },
 *     // The mismatch percentage
 *     misMatchPercentage: 2.34,
 * };
 */

Image Output

:::info The images below will only show differences as a result of running the check commands. Only the diff in a browser is shown, but the output for Android and iOS is the same. :::

<Tabs defaultValue="checkelement" values={[ {label: 'checkElement', value: 'checkelement'}, {label: 'checkScreen', value: 'checkscreen'}, {label: 'checkFullPageScreen', value: 'checkfullpagescreen'}, ]}

<TabItem value="checkelement">
js
await browser.checkElement("#__docusaurus_skipToContent_fallback > header > div > div.buttons_pzbO > a:nth-child(1)", "example-element-tag")

:::info The button text has been changed from Get Started to Getting Started! and detected as a change. :::

</TabItem>

<TabItem value="checkscreen">
js
await browser.checkScreen("example-page-tag")

:::info The button text has been changed from Get Started to Getting Started! and detected as a change. :::

</TabItem> <TabItem value="checkfullpagescreen">
js
await browser.checkFullPageScreen("full-page-tag")

:::info The button text has been changed from Get Started to Getting Started! and detected as a change. :::

</TabItem> </Tabs>

Block-Outs

Here you will find an example output for block-outs in Android NativeWebScreenshot and iOS where the status+address and toolbar are blocked out.

<Tabs defaultValue="nativeWebScreenshot" values={[ {label: 'Android nativeWebScreenshot', value: 'nativeWebScreenshot'}, {label: 'iOS', value: 'ios'}, ]}

<TabItem value="nativeWebScreenshot">

</TabItem> <TabItem value="ios">

</TabItem> </Tabs>