choo121600 opened a new pull request, #64202:
URL: https://github.com/apache/airflow/pull/64202
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
## Summary
Introduce a layered Playwright fixture system to replace fragile `beforeAll`
browser-based setup, enabling reliable data isolation and deterministic cleanup.
This change lays the foundation for safe parallel E2E execution.
## Core fixtures
- Add `fixtures/pom.ts` — POM fixtures with worker-scoped
`authenticatedRequest`
- Add `fixtures/data.ts` — worker-scoped data fixtures (`dagReady`,
`successDagRun`, `executedDagRun`, `successAndFailedRuns`) with try/finally
cleanup
*https://playwright.dev/docs/test-fixtures
*https://playwright.dev/docs/test-parallel#isolate-test-data-between-parallel-workers
## Domain-specific fixtures
- Add fixtures for asset, audit-log, calendar, dag-runs, dashboard,
task-instances, and xcom
## Utilities
- Add `utils/test-helpers.ts` — shared API utilities with UUID-based run
IDs, 409 collision recovery, and idempotent cleanup
## Test infrastructure
- Add `global-teardown.ts` — re-pauses DAGs after test run
- Update `playwright.config.ts` — add Firefox/WebKit projects,
globalTeardown, video on failure, and centralized `testConfig`
*https://playwright.dev/docs/api-testing#setup-and-teardown
This structure has been fully applied in PR #64024, where tests consistently
pass with improved stability.
<!--
Thank you for contributing!
Please provide above a brief description of the changes made in this pull
request.
Write a good git commit message following this guide:
http://chris.beams.io/posts/git-commit/
Please make sure that your code changes are covered with tests.
And in case of new features or big changes remember to adjust the
documentation.
Feel free to ping (in general) for the review if you do not see reaction for
a few days
(72 Hours is the minimum reaction time you can expect from volunteers) - we
sometimes miss notifications.
In case of an existing issue, reference it using one of the following:
* closes: #ISSUE
* related: #ISSUE
-->
---
##### Was generative AI tooling used to co-author this PR?
<!--
If generative AI tooling has been used in the process of authoring this PR,
please
change below checkbox to `[X]` followed by the name of the tool, uncomment
the "Generated-by".
-->
- [x] Yes (please specify the tool below)
claude
<!--
Generated-by: [Tool Name] following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
-->
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#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](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
