-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE] Add support for visual regression / snapshot testing #63
Comments
I have implemented this feature in a separate pytest plugin, it also supports threshold for comparing snapshots See https://github.com/kumaraditya303/pytest-playwright-snapshot Install it with $ pip install pytest-playwright-snapshot cc to some users who requested it: @TommyXie1990 @utapyngo @chasays |
There is a strong use case for including this type of testing, and my team would benefit from having this feature. Thank you for creating a separate plugin for it, though it would be great to have it baked in. |
@bgronemanLIO my tests are quite heavy on visual assertions. After trying couple of different solutions and pytest plugins I ended up with https://github.com/Visual-Regression-Tracker/Visual-Regression-Tracker - it's free, configuration is quite easy and provides reliable results. Also - it support few different comparison libs, so you can tweak the settings according to your needs. It would be nice to have this kind of feature out-of-the-box, though - but I guess it's rather unlikely. |
@aspenboy thanks for sharing that tool. It seem very robust I will consider integrating it into our pipeline. |
No problem :) good luck! |
Can you tell me when this method is planned to be implemented? |
We also need to use visual testing and would be great to know if and when this will be implemented? I didn't find any stable long term solution. |
Add support for snapshots of the page, screenshots etc like in jest
toMatchSnapshot
Example: https://github.com/kumaraditya303/pytest-playwright-snapshot
The text was updated successfully, but these errors were encountered: