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
{{ message }}
This repository has been archived by the owner on Dec 18, 2019. It is now read-only.
Our design system is broken up into dozens of individual components, each with their own set of tests.
What I'd love to see is a way to specify where all of the screenshots go per set of tests.
shots
button_shots
alert_shots
form_shots
...
This could be a value passed into the .webdrivercss() function, or better yet, allow the screenshotRoot to be relative to the test file, rather than the project root.
The text was updated successfully, but these errors were encountered:
I've found that webdrivercss is extremely restrictive if you want to integrate it into any sort of larger workflow. It seems to be suited for one person making tests against a single page.
If you try and pass different folder names to it for each test you run, you very quickly encounter problems.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Our design system is broken up into dozens of individual components, each with their own set of tests.
What I'd love to see is a way to specify where all of the screenshots go per set of tests.
This could be a value passed into the .webdrivercss() function, or better yet, allow the screenshotRoot to be relative to the test file, rather than the project root.
The text was updated successfully, but these errors were encountered: