@wdio/visual-service@9.1.3

Patch Changes

• 2a518ff: # 🐛 Bugfixes

  #1111 Pass matcher threshold to core as saveAboveTolerance

  When using visual matchers like toMatchScreenSnapshot('tag', 0.9) with alwaysSaveActualImage: false, the actual image was still being saved even when the comparison passed within the threshold.

  The root cause was that the matcher's expected threshold was not being passed to the core comparison logic. The core used saveAboveTolerance (defaulting to 0) to decide whether to save images, while the matcher used the user-provided threshold to determine pass/fail - these were disconnected.

  This fix ensures the matcher passes the expected threshold to the core as saveAboveTolerance, so images are only saved when the mismatch actually exceeds the user's acceptable threshold.

  Committers: 1

  • Wim Selles (@wswebcreation)

@wdio/visual-service@9.1.2

Patch Changes

• 0a2b6d0: ## #1111 Respect saveAboveTolerance when deciding to save actual images when alwaysSaveActualImage is false.

  When alwaysSaveActualImage is false, the actual image is no longer written to disk if the mismatch is below the configured tolerance, avoiding extra actuals when the comparison still passes.

  Committers: 1

  • Wim Selles (@wswebcreation)

• Updated dependencies [0a2b6d0]

  • @wdio/image-comparison-core@1.1.2

@wdio/image-comparison-core@1.1.2

Patch Changes

• 0a2b6d0: ## #1111 Respect saveAboveTolerance when deciding to save actual images when alwaysSaveActualImage is false.

  When alwaysSaveActualImage is false, the actual image is no longer written to disk if the mismatch is below the configured tolerance, avoiding extra actuals when the comparison still passes.

  Committers: 1

  • Wim Selles (@wswebcreation)

@wdio/visual-service@9.1.1

Patch Changes

• 340fbe6: # 🐛 Bugfixes

  #1098 Improve error message when baseline is missing and both flags are false

  When autoSaveBaseline = false and alwaysSaveActualImage = false and a baseline image doesn't exist, the error message now provides clear guidance suggesting users set alwaysSaveActualImage to true if they need the actual image to create a baseline manually.

  Committers: 1

  • Wim Selles (@wswebcreation)

• e4e5b5c: # 🐛 Bugfixes

  #1085 autoSaveBaseline collides with the new alwaysSaveActualImage flag

  When autoSaveBaseline is true and alwaysSaveActualImage is false, actual images were still saved. This patch should fix that

  Committers: 1

  • Wim Selles (@wswebcreation)

• ddf68fe: # 🐛 Bugfixes

  #1084 expect(...).toMatch*Snapshot methods do not have Promise return types

  The methods should be typed as promises

  Committers: 1

  • Wim Selles (@wswebcreation)

• Updated dependencies [340fbe6]

• Updated dependencies [e4e5b5c]

  • @wdio/image-comparison-core@1.1.1

@wdio/visual-reporter@0.4.12

Patch Changes

• e4e5b5c: # 🐛 Bugfixes

  #1085 autoSaveBaseline collides with the new alwaysSaveActualImage flag

  When autoSaveBaseline is true and alwaysSaveActualImage is false, actual images were still saved. This patch should fix that

  Committers: 1

  • Wim Selles (@wswebcreation)

@wdio/ocr-service@2.2.8

Patch Changes

• e4e5b5c: # 🐛 Bugfixes

  #1085 autoSaveBaseline collides with the new alwaysSaveActualImage flag

  When autoSaveBaseline is true and alwaysSaveActualImage is false, actual images were still saved. This patch should fix that

  Committers: 1

  • Wim Selles (@wswebcreation)

@wdio/image-comparison-core@1.1.1

Patch Changes

• 340fbe6: # 🐛 Bugfixes

  #1098 Improve error message when baseline is missing and both flags are false

  When autoSaveBaseline = false and alwaysSaveActualImage = false and a baseline image doesn't exist, the error message now provides clear guidance suggesting users set alwaysSaveActualImage to true if they need the actual image to create a baseline manually.

  Committers: 1

  • Wim Selles (@wswebcreation)

• e4e5b5c: # 🐛 Bugfixes

  #1085 autoSaveBaseline collides with the new alwaysSaveActualImage flag

  When autoSaveBaseline is true and alwaysSaveActualImage is false, actual images were still saved. This patch should fix that

  Committers: 1

  • Wim Selles (@wswebcreation)

@wdio/visual-service@9.1.0

Minor Changes

• bde4851: This PR will implement FR #1077 which is asking not to create the actual image on success. This should create a better performance because no files are writing to the system and should make sure that there's not a lot of noise in the actual folder.

  Committers: 1

  • Wim Selles (@wswebcreation)

Patch Changes

• Updated dependencies [bde4851]
  • @wdio/image-comparison-core@1.1.0

@wdio/image-comparison-core@1.1.0

Minor Changes

• bde4851: This PR will implement FR #1077 which is asking not to create the actual image on success. This should create a better performance because no files are writing to the system and should make sure that there's not a lot of noise in the actual folder.

  Committers: 1

  • Wim Selles (@wswebcreation)

@wdio/visual-service@9.0.2

Patch Changes

• 8ff1bc3: # 🐛 BugFix

  #1078: Cursor inside shadow is shown, even with disableBlinkingCursor

  Fix option "disableBlinkingCursor" to also work within shadowdom

  Committers: 1

  • Carlo Jeske (@plusgut)

• Updated dependencies [8ff1bc3]

  • @wdio/image-comparison-core@1.0.2