Hi all, With Airflow 3.0, the UI has undergone a complete revamp, and new changes are naturally more prone to regressions. We've already seen more UI regressions that are hard to catch with our current limited test coverage. Manual testing is also challenging given the wide variety of workflows and screens in the UI.
Currently, the Airflow UI has a few unit tests using Vitest and React Testing Library, but coverage is quite limited — only about 4 test files covering major pages like DagsList and TaskInstance. Many critical pages (Connections, Variables, Pools, Dashboard, etc.) have no test coverage at all. I’m exploring a two-pronged approach to improve UI testing: 1. Expand unit test coverage for individual components and pages 2. Add end-to-end (E2E) tests using Playwright for complete user workflows This would give us both component-level safety and full user-journey testing across browsers, helping catch regressions early. A few questions: - Should we prioritize expanding unit test coverage first, or work on unit and E2E tests in parallel? - For E2E testing, is Playwright a good choice, or are there other preferred tools we should explore? - If Playwright, should we use TypeScript or Python as language for tests? - Any other suggestions to strengthen our UI testing strategy? I’d love to hear your thoughts on whether this would be valuable for the project before diving into implementation details. Regards, Rahul Vats
