feat: Improve Playwright test patterns in home-dashboard.spec.ts#63448
Merged
choo121600 merged 1 commit intoapache:mainfrom Mar 13, 2026
Merged
Conversation
Contributor
Author
|
@choo121600 Could you review this PR first? |
Pyasma
pushed a commit
to Pyasma/airflow
that referenced
this pull request
Mar 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replace Playwright anti-patterns with best practices in home-dashboard spec and HomePage page object.
Changes in HomePage.ts:
button:has-text("DAG Import Errors")withgetByRole("button", { name: "DAG Import Errors" })waitFor({ state: "visible" })with web-firstexpect().toBeVisible()(2 occurrences)Changes in home-dashboard.spec.ts:
page.waitForURL()with web-firstexpect(page).toHaveURL()(2 occurrences)expect(url).toContain()assertions after URL checkscloses: #63428