Skip to content

Conversation

@dominikwilkowski
Copy link
Contributor

@dominikwilkowski dominikwilkowski commented Oct 14, 2022

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:

  • We need add documentation for this new comment. I assume into the 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

Comment on lines +3 to +7
on:
push:
branches:
- main
- next
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A11y tests now run on all pushes to main and next... worth pointing out and sense checking

Copy link
Member

@alex-page alex-page left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. Pinging @samrose3 and @aaronccasanova who also worked on snapit in case they have any thoughts.

We will also need to let folks know in #polaris slack channel about this change.

@sam-b-rose
Copy link
Member

Also looks good to me. We should update the contributing or release documentation to let people know when it is appropriate to use /vistest. Perhaps in either CONTRIBUTING.md or as part of the PR template checklist

@dominikwilkowski dominikwilkowski merged commit 724f974 into main Oct 28, 2022
@dominikwilkowski dominikwilkowski deleted the dom/ci branch October 28, 2022 00:18
sam-b-rose added a commit that referenced this pull request Oct 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants