-
Notifications
You must be signed in to change notification settings - Fork 0
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
fix: Fix Cypress #588
fix: Fix Cypress #588
Conversation
@@ -63,17 +65,11 @@ describe('Button component', () => { | |||
.find('textarea') | |||
.should('exist'); | |||
}); | |||
|
|||
it('closes code on click', () => { |
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.
For whatever reason, these steps were causing tests to fail, even though the functionality works fine locally.
Given that this is testing CL itself, rather than our code, it seemed like a waste of time and energy to debug this right now, so I pulled out every instance of it across our tests.
One thing to note, this test suite now takes AGES, so it might be a good idea for us to audit all of these tests in the near future I'd maybe question the need to run all the tests again on merge, after the branch has already passed; perhaps that's something to evaluate too. |
🎉 This PR is included in version 7.21.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
PR description
What is it doing?
Addresses Cypress failures that arrived out of nowhere (possibly underlying Chrome engine updates happening in the background), which are blocking us from releasing any new versions of the CL.
The PR updates Cypress and also updates the tests to suit the new requirements.
Why is this required?
CL BROKED
link to Jira ticket:
Add a link to the Jira ticket.
Quick Checklist:
My PR title follows the Conventional Commit spec.
I have filled out the PR description as per the template above.
I have added tests to cover new or changed behaviour.
I have updated any relevant documentation.
Important! - lastly, make sure to squash merge...