Test fails to read a snapshot after the first run, with Selenium node takeScreenshot buffer about jest-image-snapshot HOT 6 CLOSED

Yeah sorry I actually just noticed that with WebdriverIO we use saveScreenshot and don't pass it any arguments instead of screenshot:

  ...
  const screenshot = await client
    .saveScreenshot();

  expect(screenshot).toMatchImageSnapshot();

from jest-image-snapshot.

This sounds like you are not getting a png encoded buffer from Webdriver. Can you validate that it is?

from jest-image-snapshot.

@anescobar1991 I could not figure out how to validate raw bite stream but to look at the documentation of the selenium driver (everywhere says it suppose to generate a PNG) tho

  const b64 = require('base64-js')
  ...
  const buffer = await driver.takeScreenshot()
  const parsedBuffer = Buffer.from(b64.toByteArray(buffer))
  expect(parsedBuffer).toMatchImageSnapshot()

fixed it for me, tho it takes 1m to complete which is definitely not ideal

from jest-image-snapshot.

and btw sorry im blind you already have resolved an issue like that #35
thanks

from jest-image-snapshot.

@KatFishSnake I don't understand why you would need to do that, I have used it with WebdriverIO with no issues. I assume that WebdriverIO just calls selenium-webdriver?

There must be something else going on.

from jest-image-snapshot.

@anescobar1991 I assume based on what it says it returns a string <String>: screenshot The screenshot as a base64 encoded PNG.

and we need to convert that to buffer for PNG.sync.read
the same u mentioned on that #35 thread

from jest-image-snapshot.