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
Help us help you! Put down a short code snippet that illustrates your bug and
that we can run and debug locally. For example:
Describe the bug
I'm trying to implement visual comparison, but I have a lot of differences between headfull and headless testing with Chromium ( 12912 pixels (ratio 0.04 of all image pixels) are different) or perhaps that is not a lot off difference?
It works fine when testing only in headless mode. So my idea is that, I can read value of testInfo object and run visual checks only when browser is headless. But that solution does not work when running tests from the VSCode extension. And that a big issue as then I can't use your amazing locator selector and other cool features from VSCode extension.
Or perhaps there is another value in testInfo object I can check out if test run is triggered from terminal vs VSCode extension?
Add any other details about the problem here.
The text was updated successfully, but these errors were encountered:
Investigation notes: "reuse browser mode" in PlaywrightConnection forces headed browser, and this is not aligned with what the client requests, thus the discrepancy.
Proposed solution: pass --headed from the extension when running tests and make the client control whether the browser is headless. This will make "Show browser" checkbox not work for test files that explicitly call test.use({ headless: true }).
Context:
Code Snippet
Help us help you! Put down a short code snippet that illustrates your bug and
that we can run and debug locally. For example:
Describe the bug
I'm trying to implement visual comparison, but I have a lot of differences between headfull and headless testing with Chromium ( 12912 pixels (ratio 0.04 of all image pixels) are different) or perhaps that is not a lot off difference?
It works fine when testing only in headless mode. So my idea is that, I can read value of testInfo object and run visual checks only when browser is headless. But that solution does not work when running tests from the VSCode extension. And that a big issue as then I can't use your amazing locator selector and other cool features from VSCode extension.
Or perhaps there is another value in testInfo object I can check out if test run is triggered from terminal vs VSCode extension?
Add any other details about the problem here.
The text was updated successfully, but these errors were encountered: