-
-
Notifications
You must be signed in to change notification settings - Fork 9.8k
E2E: add final "open modal" part of testing-module e2e to surface server-errors #33126
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
Conversation
…and improve visibility checks for UI elements in e2e tests.
|
|
View your CI Pipeline Execution ↗ for commit 4e32302
☁️ Nx Cloud last updated this comment at |
|
Well, isn't it nice to see that the test is flaking on this PR, and we actually see why? Full error: |
… enhance error visibility during tests.
| try { | ||
| /** Sometimes the vitest instance fails, but the error-content is only shown in a modal. | ||
| * We click the link so the modal opens and we can close it. | ||
| * Having it open shortly is enough to have it be in the playwright trace, for debugging purposes. | ||
| */ | ||
| const descriptionButton = page.locator("#testing-module-description a"); | ||
| if ( | ||
| await descriptionButton.isVisible({ timeout: 4000 }).catch(() => false) | ||
| ) { | ||
| await descriptionButton.click({ timeout: 4000, force: true }); | ||
| } | ||
|
|
||
| await page.getByLabel("Close modal").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.
@valentinpalkovic Is this better?
Package BenchmarksCommit: No significant changes detected, all good. 👏 |
|
@yannbf @valentinpalkovic I've iterated a bit more, and i think this is now in a state, where it improves the debug-ability, and does not cause new issues.
Shall we merge this? |


Closes #
What I did
Checklist for Contributors
Testing
The changes in this PR are covered in the following automated tests:
Manual testing
This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!
Documentation
MIGRATION.MD
Checklist for Maintainers
When this PR is ready for testing, make sure to add
ci:normal,ci:mergedorci:dailyGH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found incode/lib/cli-storybook/src/sandbox-templates.tsMake sure this PR contains one of the labels below:
Available labels
bug: Internal changes that fixes incorrect behavior.maintenance: User-facing maintenance tasks.dependencies: Upgrading (sometimes downgrading) dependencies.build: Internal-facing build tooling & test updates. Will not show up in release changelog.cleanup: Minor cleanup style change. Will not show up in release changelog.documentation: Documentation only changes. Will not show up in release changelog.feature request: Introducing a new feature.BREAKING CHANGE: Changes that break compatibility in some way with current major version.other: Changes that don't fit in the above categories.🦋 Canary release
This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the
@storybookjs/coreteam here.core team members can create a canary release here or locally with
gh workflow run --repo storybookjs/storybook publish.yml --field pr=<PR_NUMBER>