Hi Daniel, Thanks for bringing this up. I have mixed experience with Selenium, mainly because the tests can potentially be very flaky. However, I do think it is a good idea to test some of the core functionality. I have heard a lot of good stuff regarding Cypress, some colleagues are using it, and they are quite happy with it. For example, the debugging of the failing tests is much easier.
Besides this discussion, I think we need to revamp the UI so it only goes through the REST interface. Therefore we can test the REST UI, and the interface apart from each other. This will improve the robustness of the UI and Airflow in general. Cheers, Fokko Op wo 3 apr. 2019 om 01:58 schreef Maxime Beauchemin < maximebeauche...@gmail.com>: > Side note: I'd recommend using Cypress for that. We've had a good > experience using it on Superset > https://www.cypress.io/ > > Max > > On Tue, Apr 2, 2019 at 11:23 AM Daniel Imberman (BLOOMBERG/ SAN FRAN) < > dimber...@bloomberg.net> wrote: > > > Hello fellow airflowers! > > > > I've noticed a few times on the k8s executor that when attempting to test > > the notebooks I'd find the UI on master to be broken. This made me unable > > to have full confidence in the PRs as I'm not sure if they work at the UI > > level. I wanted to see if there is any interest in creating some basic > > selenium/behave tests to ensure that PRs do not break the UI. > > > > Cheers, > > > > Daniel >
