Skip to content

Conversation

@vatsrahul1001
Copy link
Contributor

@vatsrahul1001 vatsrahul1001 commented Dec 1, 2025

This PR adds CI workflow for UI end-to-end tests introduced in #58548.

Changes

Self-contained test execution

  • breeze testing ui-e2e-tests now automatically starts Airflow with docker-compose

Workflow Integration:

  • Added run-ui-e2e-tests selective check that triggers when UI files change
  • Integrated ui-e2e-tests.yml into additional-prod-image-tests.yml
  • Kept workflow_dispatch for manual triggering

Testing

Run locally:
breeze testing ui-e2e-tests

Also Tested in CI as current PR has UI changes
image


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

@boring-cyborg boring-cyborg bot added area:dev-tools area:UI Related to UI/UX. For Frontend Developers. backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch labels Dec 1, 2025
@vatsrahul1001 vatsrahul1001 removed the backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch label Dec 1, 2025
@vatsrahul1001 vatsrahul1001 force-pushed the ci-workflow-ui-e2e branch 5 times, most recently from 89483a2 to d7e9297 Compare December 9, 2025 10:59
@vatsrahul1001
Copy link
Contributor Author

Until the test suite becomes too long to run. (>15 minutes for instance). I would say we run them in all UI PRs, just to be sure.

We can move that to canary build and only a subset of critical ones if the test suites grows too big.

@pierrejeambrun updated workflow to run for every UI changes with all browsers

Copy link
Member

@potiuk potiuk left a comment

Choose a reason for hiding this comment

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

Nice!

@potiuk
Copy link
Member

potiuk commented Dec 9, 2025

Until the test suite becomes too long to run. (>15 minutes for instance). I would say we run them in all UI PRs, just to be sure.

We can move that to canary build and only a subset of critical ones if the test suites grows too big.

We can also split them to paralel suites using matrix job, this way the elapsed time will be shorter, we will increase build time spent, but we are still way below the limits that ASF has per-project. We did it successfully for a number of other jobs.

@vatsrahul1001 vatsrahul1001 merged commit 1e7e40e into apache:main Dec 10, 2025
124 checks passed
@vatsrahul1001 vatsrahul1001 deleted the ci-workflow-ui-e2e branch December 10, 2025 08:45
@jscheffl
Copy link
Contributor

@vatsrahul1001 seems canary tests are now broken in Chromium, can you check what is broken (I do not understand the root of the problem :-D need to lern how this works...) --> https://github.com/apache/airflow/actions/runs/20110899789/job/57714593194

@vatsrahul1001
Copy link
Contributor Author

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

Labels

area:dev-tools area:UI Related to UI/UX. For Frontend Developers.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants