-
69d25fe: Multiple fixes:
- update deps
- fix #728: Missing Type Information in Service Configuration
- fix #745: The image comparison process stalls when utilizing the checkElement method to compare screenshots of two different elements
- 2d033e8: #691 Add option to ignore blinking cursors / carets
- Updated dependencies [2d033e8]
- 4a4adf1: Fix resize dimensions for mobile
- 4a4adf1: update deps
-
1df5350: # Improve iPhone support
- Mobile: support iOS 18 and the iPhone 16 series for the blockouts
- Mobile: don't use the device blockouts for element screenshot
- Mobile: when the blockouts had the value
{x: 0, y: 0, width: 0, height: 0}then Resemble picked this up as a full blockout. This caused false positives for iOS
- 786248e: Upgrade Jimp to the latest major
This solves the issue 425 of removing a diff image from the diff folder for success. We now remove the "previous" diff image before we execute the compare so we also have the latest, or we now have a diff image after a retry where the first run failed and produced an image and a new successful run.
We've update all dependencies.
- Wim Selles (@wswebcreation)
- 9fdb2d2: feat: work with V9
-
85a1d82: # 🐛 Bug Fixes
Fix issues:
- update dependencies
- Wim Selles (@wswebcreation)
-
0b01b64: ### @wdio/visual-service
Added Reporting output You now have the option to export the compare results into a JSON report file. By enabling the module option
createJsonReportFiles: true, each image that is compared will create a report stored in theactualfolder, next to eachactualimage result.The output will look like this:
{ "parent": "check methods", "test": "should fail comparing with a baseline", "tag": "examplePageFail", "instanceData": { "browser": { "name": "chrome-headless-shell", "version": "126.0.6478.183" }, "platform": { "name": "mac", "version": "not-known" } }, "commandName": "checkScreen", "boundingBoxes": { "diffBoundingBoxes": [ { "left": 1088, "top": 717, "right": 1186, "bottom": 730 } //.... ], "ignoredBoxes": [ { "left": 159, "top": 652, "right": 356, "bottom": 703 } //... ] }, "fileData": { "actualFilePath": "/Users/wswebcreation/Git/wdio/visual-testing/.tmp/actual/desktop_chrome-headless-shellexamplePageFail-local-chrome-latest-1366x768.png", "baselineFilePath": "/Users/wswebcreation/Git/wdio/visual-testing/localBaseline/desktop_chrome-headless-shellexamplePageFail-local-chrome-latest-1366x768.png", "diffFilePath": "/Users/wswebcreation/Git/wdio/visual-testing/.tmp/diff/desktop_chrome-headless-shell/examplePageFail-local-chrome-latest-1366x768png", "fileName": "examplePageFail-local-chrome-latest-1366x768.png", "size": { "actual": { "height": 768, "width": 1366 }, "baseline": { "height": 768, "width": 1366 }, "diff": { "height": 768, "width": 1366 } } }, "misMatchPercentage": "12.90", "rawMisMatchPercentage": 12.900729014153246 }When all tests are executed, a new JSON file with the collection of the comparisons will be generated and can be found in the root of your actual folder. The data is grouped by:
describefor Jasmine/Mocha orFeaturefor CucumberJSitfor Jasmine/Mocha orScenariofor CucumberJS
and then sorted by:
commandName, which are the compare method names used to compare the imagesinstanceData, browser first, then device, then platform
it will look like this
[ { "description": "check methods", "data": [ { "test": "should fail comparing with a baseline", "data": [ { "tag": "examplePageFail", "instanceData": {}, "commandName": "checkScreen", "framework": "mocha", "boundingBoxes": { "diffBoundingBoxes": [], "ignoredBoxes": [] }, "fileData": {}, "misMatchPercentage": "14.34", "rawMisMatchPercentage": 14.335403703025868 }, { "tag": "exampleElementFail", "instanceData": {}, "commandName": "checkElement", "framework": "mocha", "boundingBoxes": { "diffBoundingBoxes": [], "ignoredBoxes": [] }, "fileData": {}, "misMatchPercentage": "1.34", "rawMisMatchPercentage": 1.335403703025868 } ] } ] } ]The report data will give you the opportunity to build your own visual report without doing all the magic and data collection yourself.
- Add support to generate single JSON report files
- Refactored the CLI to use
@inquirer/promptsinstead ofinquirer
- Wim Selles (@wswebcreation)
- Update deps
- Wim Selles (@wswebcreation)
- 169b7c5: fix(webdriver-image-comparison): export WicElement
-
66b9f11: # 💥 Breaking
This PR replaces Canvas as a dependency with Jimp. This removes the need to use system dependencies and will reduce the number of system dependency errors/issues (node-gyp/canvas and so on). This will, in the end, make the life of our end users way easier due to:
- less errors
- less complex test environments
[!note] Extensive research has been done and we have chosen to "fork" ResembleJS, adjust it by making use of Jimp instead of Canvas and break the browser API because the fork will only be used in a nodejs environment Investigation showed that creating a wrapper would even make it slower, so we went for the breaking change in the API by just replacing Canvas with Jimp
[!important] There is a performance impact where Canvas is around 70% faster than Jimp. This has been measured without using WebdriverIO and only comparing images. When the "old" implementation with WebdriverIO combined with Canvas or Jimp is compared, we hardly see a performance impact.
Update the baseline images through the command line by adding the argument
--update-visual-baseline. This will- automatically copy the actual take screenshot and put it in the baseline folder
- if there are differences it will let the test pass because the baseline has been updated
Usage:
npm run test.local.desktop --update-visual-baseline
When running logs info/debug mode you will see the following logs added
[0-0] .............. [0-0] ##################################################################################### [0-0] INFO: [0-0] Updated the actual image to [0-0] /Users/wswebcreation/Git/wdio/visual-testing/localBaseline/chromel/demo-chrome-1366x768.png [0-0] ##################################################################################### [0-0] ..........- remove Vitest fix
- add app images
- update the build
- c9fab82: change console.log to wdio logger
-
f878cab: # 🚀 Feature
- Add device support for Storybook, it can be used like this
npx wdio tests/configs/wdio.local.desktop.storybook.conf.ts --storybook --devices="iPhone 14 Pro Max","Pixel 3 XL"
- Wim Selles (@wswebcreation)
-
b717d9a: # 💥 Breaking changes
- the new element screenshot is producing "smaller" screenshots on certain Android OS versions (not all), but it's more "accurate" so we accept this
Automatically scan local/remote storybook instances to create element screenshots of each component by adding
export const config: WebdriverIO.Config = { // ... services: ["visual"], // .... };
to your
servicesand runningnpx wdio tests/configs/wdio.local.desktop.storybook.conf.ts --storybookthrough the command line. It will automatically use Chrome. The following options can be provided through the command line-
--headless, defaults totrue -
--numShards {number}, this will be the amount of parallel instances that will be used to run the stories. This will be limited by themaxInstancesin yourwdio.conf-file. When running inheadless-mode then do not increase the number to more than 20 to prevent flakiness -
--clip {boolean}, try to take an element instead of a viewport screenshot, defaults totrue -
--clipSelector {string}, this is the selector that will be used to:- select the element to take the screenshot of
- the element to wait for to be visible before a screenshot is taken
defaults to
#storybook-root > :first-childfor V7 and#root > :first-child:not(script):not(style)for V6 -
--version, the version of storybook, defaults to 7. This is needed to know if the V6clipSelectorneeds to be used. -
--browsers {edge,chrome,safari,firefox}, defaults to Chrome -
--skipStories, this can be:- a string (
example-button--secondary,example-button--small) - or a regex (
"/.*button.*/gm") to skip certain stories
- a string (
You can also provide service options
export const config: WebdriverIO.Config = { // ... services: [ [ 'visual', { // Some default options baselineFolder: join(process.cwd(), './__snapshots__/'), debug: true, // The storybook options storybook: { clip: false, clipSelector: ''#some-id, numShards: 4, skipStories: ['example-button--secondary', 'example-button--small'], url: 'https://www.bbc.co.uk/iplayer/storybook/', version: 6, }, }, ], ], // .... }
The baseline images will be stored in the following structure:
{projectRoot} |_`__snapshots__` |_`{category}` |_`{componentName}` |_{browserName} |_`{{component-id}-element-{browser}-{resolution}-dpr-{dprValue}}.png`which will look like this
[!NOTE] Storybook 6.5 or higher is supported
hideScrollBarsis disabled by default when using the Storybook runner- By default, all element screenshots in the browser, except for iOS, will use the native method to take element screenshots. This will make taking an element screenshot more than 5% faster. If it fails it will fall back to the "viewport" screenshot and create a cropped element screenshot.
- Taking an element screenshot becomes 70% faster due to removing the fixed scroll delay of 500ms and changing the default scrolling behaviour to an instant scroll
- refactor web element screenshots and update the screenshots
- added more UTs to increase the coverage
- When the element has no height or width, we default to the viewport screen size to prevent not cropping any screenshot. An error like below will be logged in red
The element has no width or height. We defaulted to the viewport screen size of width: ${width} and height: ${height}.- There were cases where element screenshots were automatically rotated which was not intended
- 43ed502: Add font loading features:
- add
waitForFontsLoadedso the module automatically waits for all fonts to be loaded, enabled by default - add
enableLayoutTestingso all text will become transparent so- font rendering issues won't cause flakiness
- image comparison can be done on layout
- add
- c8fdcd3: Fix to override visibility/display value
- fd74a35: (feat): set default baseline folder next to test file
-
ef386b6: # 💥 Breaking changes:
resizeDimensionson the element can now only be an object, it has been deprecated for a while
- Next to supporting Web snapshot testing this module now also supports 💥 Native App 💥 snapshot testing. The methods
saveElement|checkElement | saveScreen | checkScreenand the matcherstoMatchElementSnapshot | toMatchScreenSnapshotare available for Native Apps
[!NOTE] This module will automatically detect the context (web | webview | native_app) and will handle all complex logic for you
The methods
saveFullPageScreen | checkFullPageScreen | saveTabbablePage|checkTabbablePagewill throw an error when they are used in the native context for native mobile apps and will look like this$ wdio tests/configs/wdio.local.android.emus.app.conf.ts Execution of 1 workers started at 2024-01-30T06:18:24.865Z [0-0] RUNNING in Android - file:///tests/specs/mobile.app.spec.ts [0-0] Error in "@wdio/visual-service mobile app.should compare a screen successful for 'Pixel_7_Pro_Android_14_API_34' in PORTRAIT-mode" Error: The method saveFullPageScreen is not supported in native context for native mobile apps! at /wdio/visual-testing/packages/webdriver-image-comparison/src/commands/saveFullPageScreen.ts:26:15 at step (/wdio/visual-testing/packages/webdriver-image-comparison/dist/commands/saveFullPageScreen.js:33:23) at Object.next (/wdio/visual-testing/packages/webdriver-image-comparison/dist/commands/saveFullPageScreen.js:14:53) at /wdio/visual-testing/packages/webdriver-image-comparison/dist/commands/saveFullPageScreen.js:8:71 at new Promise (<anonymous>) at __awaiter (/wdio/visual-testing/packages/webdriver-image-comparison/dist/commands/saveFullPageScreen.js:4:12) at saveFullPageScreen (/wdio/visual-testing/packages/webdriver-image-comparison/dist/commands/saveFullPageScreen.js:47:12) at Browser.<anonymous> (file:///wdio/visual-testing/packages/service/dist/service.js:101:24) [0-0] FAILED in Android - file:///tests/specs/mobile.app.spec.ts "spec" Reporter: ------------------------------------------------------------------ [/wdio/visual-testing/apps/app.apk Android #0-0] Running: /wdio/visual-testing/apps/app.apk on Android [/wdio/visual-testing/apps/app.apk Android #0-0] Session ID: c1101184-e3d5-42b5-a31f-8ebaa211f1a1 [/wdio/visual-testing/apps/app.apk Android #0-0] [/wdio/visual-testing/apps/app.apk Android #0-0] » /tests/specs/mobile.app.spec.ts [/wdio/visual-testing/apps/app.apk Android #0-0] @wdio/visual-service mobile app [/wdio/visual-testing/apps/app.apk Android #0-0] ✖ should compare a screen successful for 'Pixel_7_Pro_Android_14_API_34' in PORTRAIT-mode [/wdio/visual-testing/apps/app.apk Android #0-0] [/wdio/visual-testing/apps/app.apk Android #0-0] 1 failing (1.5s) [/wdio/visual-testing/apps/app.apk Android #0-0] [/wdio/visual-testing/apps/app.apk Android #0-0] 1) @wdio/visual-service mobile app should compare a screen successful for 'Pixel_7_Pro_Android_14_API_34' in PORTRAIT-mode [/wdio/visual-testing/apps/app.apk Android #0-0] The method saveFullPageScreen is not supported in native context for native mobile apps! [/wdio/visual-testing/apps/app.apk Android #0-0] Error: The method saveFullPageScreen is not supported in native context for native mobile apps! [/wdio/visual-testing/apps/app.apk Android #0-0] at /wdio/visual-testing/packages/webdriver-image-comparison/src/commands/saveFullPageScreen.ts:26:15 [/wdio/visual-testing/apps/app.apk Android #0-0] at step (/wdio/visual-testing/packages/webdriver-image-comparison/dist/commands/saveFullPageScreen.js:33:23) [/wdio/visual-testing/apps/app.apk Android #0-0] at Object.next (/wdio/visual-testing/packages/webdriver-image-comparison/dist/commands/saveFullPageScreen.js:14:53) [/wdio/visual-testing/apps/app.apk Android #0-0] at /wdio/visual-testing/packages/webdriver-image-comparison/dist/commands/saveFullPageScreen.js:8:71 [/wdio/visual-testing/apps/app.apk Android #0-0] at new Promise (<anonymous>) [/wdio/visual-testing/apps/app.apk Android #0-0] at __awaiter (/wdio/visual-testing/packages/webdriver-image-comparison/dist/commands/saveFullPageScreen.js:4:12) [/wdio/visual-testing/apps/app.apk Android #0-0] at saveFullPageScreen (/wdio/visual-testing/packages/webdriver-image-comparison/dist/commands/saveFullPageScreen.js:47:12) [/wdio/visual-testing/apps/app.apk Android #0-0] at Browser.<anonymous> (file:///wdio/visual-testing/packages/service/dist/service.js:101:24) Spec Files: 0 passed, 1 failed, 1 total (100% completed) in 00:00:11 error Command failed with exit code 1.autoSaveBaselineis true by default, so if no baseline images are present it will automatically create a new baseline- Mobile screenshots of the complete screen now automatically exclude all native OS elements like the notification bar, home bar, address bar, and so on, the settings
blockOutSideBar | blockOutStatusBar |blockOutToolBarare now all defaulted totrue
- element screenshots could also get resized dimensions, which would cut out a bigger portion around the element. This was failing when the dimensions got out of the boundaries of the official screenshot. This has now been fixed with:
- not going outside of the screenshot
- log extra warnings
- 488d424: (docs): update readme
- 36d3868: Support for WebdriverIO v8
