You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
I have noticed in release-notes for 1.3.5 there was a nice feature added: Screenshot in test-report.
However, I couldn't find any documentation on how to enable that, so I assumed it works out-of-the-box.
So I did a sample project to see how it works and it doesn't work there. No errors also seen in logs.
Could be a bug, or what am I doing wrong? :)
Noticed in this PR (#1675) a screenshot of how it works. Doesn't work for me though... is there a special setup that needs to be done, or some "enable"-flag to turn on?
So running verify task in your sample repo showed an error where the original file did not exist
Then running record, changing the test text from `"Hello Brother" to "Hello Sister Sister" did not show the delta image in the test report.
It looks like the main issue is your package name seems to break our delimiter _ in the filename of generated snapshots.
I was able to change package name references from "com.example.test_paparazzi" to "com.example.testpaparazzi" and rerun the suggested steps and it provided the correct output.
Our filename parsing for diffs is pretty brittle. I think going forward we plan on generating a manifest file in our verification output to better solve this problem.
Description
I have noticed in release-notes for 1.3.5 there was a nice feature added: Screenshot in test-report.
However, I couldn't find any documentation on how to enable that, so I assumed it works out-of-the-box.
So I did a sample project to see how it works and it doesn't work there. No errors also seen in logs.
Could be a bug, or what am I doing wrong? :)
Steps to Reproduce
PaparazziScreenshotDeltaTest
file, that does a simple screenshot test.Expected behavior
I expected to see delta images in the output failure report.
Additional information:
Screenshots
The text was updated successfully, but these errors were encountered: