X Tutup
Skip to content

feat: Improve Playwright test patterns in dag-runs-tab.spec.ts#63189

Open
Desel72 wants to merge 2 commits intoapache:mainfrom
Desel72:fix/improve-playwright-dag-runs-tab-patterns
Open

feat: Improve Playwright test patterns in dag-runs-tab.spec.ts#63189
Desel72 wants to merge 2 commits intoapache:mainfrom
Desel72:fix/improve-playwright-dag-runs-tab-patterns

Conversation

@Desel72
Copy link

@Desel72 Desel72 commented Mar 9, 2026

Improve Playwright test patterns in dag-runs-tab.spec.ts

Replace anti-patterns in DagRunsTabPage.ts and dag-runs-tab.spec.ts with
Playwright best practices:

  • Replace page.locator('[data-testid="..."]') with page.getByTestId("...")
  • Replace CSS a[href...] selectors with getByRole("link") locators
  • Replace imperative page.waitForURL() with web-first expect(page).toHaveURL()
  • Replace locator("tbody tr") with locator("tbody").getByRole("row")

This PR focuses on improving test patterns only. It does not change test
coverage or behavior.

closes: #63165


Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)

  • Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
  • For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
  • When adding dependency, check compliance with the ASF 3rd Party License Policy.
  • For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

@boring-cyborg
Copy link

boring-cyborg bot commented Mar 9, 2026

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

  • Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
  • In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
  • Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
  • Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
  • Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
  • Be sure to read the Airflow Coding style.
  • Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
    Apache Airflow is a community-driven project and together we are making it better 🚀.
    In case of doubts contact the developers at:
    Mailing List: dev@airflow.apache.org
    Slack: https://s.apache.org/airflow-slack

@boring-cyborg boring-cyborg bot added the area:UI Related to UI/UX. For Frontend Developers. label Mar 9, 2026
@Desel72
Copy link
Author

Desel72 commented Mar 9, 2026

Hi @choo121600 Please review this pr and share any feedback. thank you

Copy link
Member

@choo121600 choo121600 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like the test is failing.
Could you check it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:UI Related to UI/UX. For Frontend Developers.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

E2E: Improve Playwright test patterns in dag-runs-tab.spec.ts

2 participants

X Tutup