-
Notifications
You must be signed in to change notification settings - Fork 327
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
Clean up integration tests and add listeners for backend calls #11847
Conversation
d6030af
to
c796cde
Compare
🧪 Storybook is successfully deployed!📊 Dashboard:
|
|
||
setup('authenticate', ({ page }) => { | ||
const authFilePath = actions.getAuthFilePath() | ||
setup.slow() |
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.
btw, why we need to setup.slow()
here?
@@ -1,35 +1,39 @@ | |||
/** @file Test the login flow. */ | |||
import { expect, test, type Page } from '@playwright/test' | |||
// import { expect, test, type Page } from '@playwright/test' |
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.
Can we use test.skip here?
@@ -1,31 +1,34 @@ | |||
/** @file Test the "change password" modal. */ | |||
import { expect, test, type Page } from '@playwright/test' | |||
// import { expect, test, type Page } from '@playwright/test' |
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.
Same here
- Close enso-org/cloud-v2#1604 - Add ability to track backend calls - Remove inconsistent integration test code - Add skeleton classes for settings pages # Important Notes None (cherry picked from commit b83c5a1)
Pull Request Description
Important Notes
None
Testing Instructions
N/A - there are no changes to the codebase outside of tests
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:
Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.Scala,
Java,
TypeScript,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
Unit tests have been written where possible.If meaningful changes were made to logic or tests affecting Enso Cloud integration in the libraries,or the Snowflake database integration, a run of the Extra Tests has been scheduled.
If applicable, it is suggested to paste a link to a successful run of the Extra Tests.