-
Notifications
You must be signed in to change notification settings - Fork 323
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
Add traces to integration tests + suppress one flaky assertion. #11595
base: develop
Are you sure you want to change the base?
Conversation
ff787de
to
43bbad4
Compare
b8089aa
to
b91e7c4
Compare
b91e7c4
to
c078f4d
Compare
🧪 Storybook is successfully deployed!📊 Dashboard:
|
await expect(writeNode.locator('.TableVisualization')).toContainText(OUTPUT_FILE) | ||
} catch { | ||
// TODO[ao] | ||
// The above check is flaky, because sometimes the additional egine run overrides node output back to "dry run". |
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.
egine
-> engine
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.
approving rename of dashboard files only
might wanna update codeowners too due to the change of path |
@farmaazon why we run |
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.
See the comment above
697bf06
to
7092738
Compare
…/fix-integration-test
…/fix-integration-test
Pull Request Description
Fixes #11604
Most issues were caused by a problem with Project List flooding the network with its requests - this was fixed on develop.
But one assertion was flaky - it assumed we will see the "real" run result on
write
node, but sometimes it is immediately overwritten by dry run.But the most important part of this PR is adding traces to Electron packages - it's should be much easier now to debug E2E test failures.
Also renamed the previously misnamed "E2E tests" to "[GUI] integration tests".
Important Notes
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.