-
Notifications
You must be signed in to change notification settings - Fork 2
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
Feature/cypress testing #121
base: develop
Are you sure you want to change the base?
Conversation
# Conflicts: # app/client/src/components/welcome.tsx
# Conflicts: # app/client/src/components/welcome.tsx
# Conflicts: # app/client/src/routes/allRebates.tsx # app/client/src/routes/helpdesk.tsx # app/client/src/routes/newRebate.tsx
…f the test files.
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
@courtneymyers I think I am done making the switch to
|
# Conflicts: # app/package-lock.json # app/package.json
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Adds cypress automated tests and code coverage.
Notes:
/* istanbul ignore next: cannot test */
flags before some instances of code that cannot be tested (i.e., reportWebVitals and unhandled exceptions). This improves the code coverage numbers.retries
flag to the cypress config. This makes cypress retry a test if it fails.Cypress.on('uncaught:exception',...
to the top of all of our.spec.js
files. This makes it so that cypress does not fail tests when there are errors in the chrome developer console. I put a todo comment to remind us to remove this code when the app is more stable. The screenshot below shows the error message that usually causes tests to fail.