Test: Add E2E tests for Assets Page

[sarth-akvaish]

This PR adds the E2E tests for Assets Page.

The test now verfies:

• Assets are listed in the table
• Asset name are visible
• Clicking on an asset name navigates to asset detail page
• working of search filters and pagination

Closes : #59929

---

^ 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.

[vatsrahul1001]

@sarth-akvaish can you look at failing tests?

[vatsrahul1001]

@sarth-akvaish Thanks for the PR! A few things to address:

1. Add beforeAll to trigger producer DAG - Tests assume assets exist. Add setup that unpause consumer DAG and triggers asset_produces_1 to create real asset data:
   test.beforeAll(async ({ browser }) => {
   // Trigger asset_produces_1 to create asset data
   });

Also maybe trigger multiple dags which uses assets and it will help in search test to filter
2. Coordinate with PR #59939 - Both PRs create different page objects. Work together to use single AssetsPage.ts and assets.spec.ts

3. Test naming - Use "verify" prefix
4. Fix fragile selectors - Be more specific
5. Pagination - Use ?offset=0&limit=1 URL param

Let me know if you have questions

[sarth-akvaish]

@sarth-akvaish Thanks for the PR! A few things to address:

1. Add beforeAll to trigger producer DAG - Tests assume assets exist. Add setup that unpause consumer DAG and triggers asset_produces_1 to create real asset data:
   test.beforeAll(async ({ browser }) => {
   // Trigger asset_produces_1 to create asset data
   });

Also maybe trigger multiple dags which uses assets and it will help in search test to filter 2. Coordinate with PR #59939 - Both PRs create different page objects. Work together to use single AssetsPage.ts and assets.spec.ts

3. Test naming - Use "verify" prefix
4. Fix fragile selectors - Be more specific
5. Pagination - Use ?offset=0&limit=1 URL param

Let me know if you have questions

Hi @vatsrahul1001, Thanks for the review. I’ll incorporate the suggested changes and update the PR.

[sarth-akvaish]

Hi @vatsrahul1001 , currently in beforeAll I'm triggering a DAG, and checking its status in the run tab (using polling), Should I have to check the status of Dag run ? If yes, then current one is giving flaky test, can I test using rest api endpoints?

[vatsrahul1001]

Hi @vatsrahul1001 , currently in beforeAll I'm triggering a DAG, and checking its status in the run tab (using polling), Should I have to check the status of Dag run ? If yes, then current one is giving flaky test, can I test using rest api endpoints?

Yes we can use RESTAPI and have added this in suggested change

[vatsrahul1001]

@sarth-akvaish we are missing test for verify clicking asset navigates to detail page

[vatsrahul1001]

Great work @sarth-akvaish merging the PR