One size fits all

This release changes:

• The method kamera uses to resize chrome to contents. Previously it used those exposed by chrome dev protocol but now evaluates javascript #30

This release adds support for:

• Specifying the dom element to resize the browser to #30 (thanks @jleonard-r7 and @johanatan)
• Asserting that there is at least one test #25
• deps.edn #28 (thanks @johanatan)
• The dssim algorithm #33 (thanks @johanatan and @jleonard-r7)

This release improves:

• The element-exists? predicate is now more forgiving #27

Seedy Pea

This release changes:

• kamera now uses clj-chrome-devtools instead of webfolder/cdp4j #5. If you used the session parameter in any of the callback hooks you will need to update your code. Additionally the :chrome-options config setting has changed, see the README for an example.
• The browser window is now resized to fit the content height only before taking a screenshot by default. This behaviour is controlled by the :resize-to-contents option, see the README

This release fixes:

• Expand / contract icons in the report not showing up properly

Size isn't everything

This release changes:

• The browser window is no longer resized to fit the contents before taking a screenshot by default. This caused issues with responsive CSS which could trip a breakpoint and make the display render differently to that expected. This behaviour can be re-enabled by setting the :resize-to-contents? option to true.

This release adds support for:

• The :assert? option (enabled by default) allows you to decide whether to assert that the actual image matches the expected image - good for when you just want to capture a screenshot without asserting, or to disable a test

Report!

Kamera now generates a report allowing side-by-side comparisons of actual, expected and difference images, including a linked magnifier to inspect small details. Also included is quick navigation, filtering and a display of the normalisation steps.