-
Notifications
You must be signed in to change notification settings - Fork 179
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
test(ll): make cypress tests compatible with deployed environments #16405
Conversation
Fixed. Removed the mock and replaced with real file read. |
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.
love this. your file saver approach is honestly way better than the mocked file saver we used before, we should do the same thing for PD
const testAliases: {} | { 'file-saver': string } = | ||
process.env.CYPRESS === '1' | ||
? { | ||
'file-saver': | ||
path.resolve(__dirname, 'cypress/mocks/file-saver.js') ?? '', | ||
} | ||
: {} | ||
|
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.
these deletions make me so happy
Overview
Labware Library Cypress tests were able to run locally and in CI but some patterns did not allow for the same test to execute against a deployed environment. Additionally there were no instructions or make targets to quickly run the tests against a deployed environment.
Test Plan and Hands on Testing
make -C labware-library test-e2e-remote REMOTE_BASE_URL='https://labware.opentrons.com'
labware library e2e tests
job inLabware Library test, build, and deploy
proves the tests also still works against localhostReview requests
Risk assessment