-
Notifications
You must be signed in to change notification settings - Fork 81
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
Playwright testing #478
Playwright testing #478
Conversation
…ng the default GITHUB_TOKEN
@sergiobeltranguerrero @marcgc21 requested that the production is tested. I can look into testing development as well sometime later. |
# Conflicts: # .github/workflows/ishikawa-tools.yml # ishikawa_tools/ishikawa_tools_script.py # package.json
|
Quality Gate failedFailed conditions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Your Pull Request will be approved and your changes will be added to the newest version of develop, and i will check if everything is working fine!
This PR adds adds playwright UI tests, as well as a github action that runs them. This is part of the quality controll subject of which Marc is the professor. Attention should be payed to the change in the Jest configuration. As it stands right now any test contained in a folder called e2e (at any depth) will be ignored by Jest. This change was required because the last configuration was matching any files ending in .spec.js and tried to run playwright tests as unit test and therefore the test GH action would always fail.