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
settings.test.js will fail all test cases unless connect.test.js is run first.
Reason
This is because the user is not logged into their Mailchimp account
Solution
The connect.test.js test suite contains the steps to connect a user with their Mailchimp account for the first time. This code can be repurposed to log a user into their Mailchimp account before any tests are run. In addition, conditional checks can be put in place in case a user is already logged in.
Steps to Reproduce
Set up your local testing environment according to the E2E tests readme
Run npm run cypress:open to open the Cypress UI. This will allow you to run test suites separately.
Run connect.test.js Every test case will fail because the user is not logged in to their Mailchimp account.
Screenshots, screen recording, code snippet
No response
Environment information
Device: MacBook Air M3 2024
OS: 14.6
WordPress information
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Describe the bug
Problem
settings.test.js
will fail all test cases unlessconnect.test.js
is run first.Reason
This is because the user is not logged into their Mailchimp account
Solution
The
connect.test.js
test suite contains the steps to connect a user with their Mailchimp account for the first time. This code can be repurposed to log a user into their Mailchimp account before any tests are run. In addition, conditional checks can be put in place in case a user is already logged in.Steps to Reproduce
npm run cypress:open
to open the Cypress UI. This will allow you to run test suites separately.connect.test.js
Every test case will fail because the user is not logged in to their Mailchimp account.Screenshots, screen recording, code snippet
No response
Environment information
WordPress information
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: