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
Separated a11y and vis tests and made vis test be triggered by /vistest (#7402)
Running the vis tests cost money and we don't need them run on each
merge to `main`. We should eventually move off of storybook and run real
visual regression testing but until then let's make the vis tests be
triggered by a comment `/vistest` and go from there.
TODO:
- [x] We need add documentation for this new comment. I assume into the
[`CONTRIBUTING.md`](https://github.com/Shopify/polaris/blob/00449becb15df24d22d7d062e2e20cda7c14d954/.github/CONTRIBUTING.md)
file?
- [ ] Test the workflow. I moved things and merged things in. in theory
this should work but I have not tested it yet
Copy file name to clipboardExpand all lines: .github/CONTRIBUTING.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -155,6 +155,7 @@ We recommend running tests as well as trying your build of a package in a real p
155
155
156
156
-`yarn test` will run tests for all packages
157
157
-`yarn turbo run test --filter="[HEAD^1]"` will test any package that has changed in the last commit
158
+
- Run visual testing via adding the `/vistest` comment in a PR
158
159
159
160
You can test your changes in another project locally by creating a [snapshot release](https://github.com/Shopify/polaris/blob/main/documentation/Releasing.md#snapshot-release).
0 commit comments