Add CI workflow for UI e2e tests#58901
Conversation
)" This reverts commit 416c73e.
89483a2 to
d7e9297
Compare
d7e9297 to
2078ba4
Compare
8e9b02b to
2000be6
Compare
@pierrejeambrun updated workflow to run for every UI changes with all browsers |
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 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 |
Add CI workflow for UI e2e tests (apache#58901)
This PR adds CI workflow for UI end-to-end tests introduced in #58548.
Changes
Self-contained test execution
breeze testing ui-e2e-testsnow automatically starts Airflow with docker-composeWorkflow Integration:
Testing
Run locally:
breeze testing ui-e2e-tests
Also Tested in CI as current PR has UI changes

^ 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.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.