airflow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Driesprong, Fokko" <fo...@driesprong.frl>
Subject Re: Airflow end-to-end testing
Date Sun, 14 Apr 2019 18:53:00 GMT
Hi Chris,

Having some UI testing would be a great addition to Airflow's testing
framework. However, I have some bad experiences with Selenium. In projects
that I've worked with selenium, it was always very flaky, and hard to
debug. Since we haven't written any tests, my first step would be to pick
the technology to write the tests. As I've already mentioned in the thread
that Kamil pasted, I would like to consider Cypress for testing the UI.
Cypress comes with a nice UI where you can easily see when the test failed.
In Selenium this is still a hassle.

I would start with some simple scenario's. Starting Airflow and kicking off
an example dag, and make sure that it runs in the UI.

Cheers, Fokko




Op vr 12 apr. 2019 om 17:21 schreef Kamil Breguła <kamil.bregula@polidea.com
>:

> Similar discusion:
>
> https://lists.apache.org/thread.html/0480a042107a153468f5ce1e34548e018ffbf69730ff056895ab5829@%3Cdev.airflow.apache.org%3E
>
> On Fri, Apr 12, 2019 at 2:39 PM Chris Korakidis <c.korakidis@gmail.com>
> wrote:
>
> > Hi,
> >
> > Asimina is looking for an open source project to contribute to as an
> > automation tester.
> >
> > My colleague Kaxil Naik contributes to airflow and I was told you don't
> > have any automation testing in place yet.
> >
> > I think that would be a good opportunity for both sides to setup an
> > automation testing project for airflow.
> >
> > Asimina is familiar with Java and Selenium and she would be able to setup
> > an automation testing project for airflow. That would be a separate
> > project, so as to keep the airflow clean. The Java code will be simple,
> > mainly using the Selenium API. I can help with reviewing and code quality
> > concerns if needed.
> > Tech stack will be Maven, Selenium, Cucumber. You can get an idea of how
> it
> > will look like if you take a look at a POC:
> > https://github.com/AsiminaAth/cwjobsit
> > You'll find both JUnit and Cucumber approaches there, just Cucumber would
> > be OK for end-to-end testing.
> >
> > Main things Asimina will need are:
> > Having the project setup and granting her access to the project
> > Having the project added to some CI server
> > Having support in terms of priorities regarding the scenarios and
> features
> > to be tested.
> >
> > Please let me know what are your thoughts.
> > Regards,
> > Chris
> >
> > --
> > Christakis Korakidis
> > Senior Software Engineer <https://goo.gl/UZUmTN>
> > http://www.linkedin.com/in/ckorakidis
> > skype: ckorakidis
> >
>
>
> --
>
> Kamil Breguła
> Polidea <https://www.polidea.com/> | Software Engineer
>
> M: +48 505 458 451 <+48505458451>
> E: kamil.bregula@polidea.com
> [image: Polidea] <https://www.polidea.com/>
>
> We create human & business stories through technology.
> Check out our projects! <https://www.polidea.com/our-work>
> [image: Github] <https://github.com/Polidea> [image: Facebook]
> <https://www.facebook.com/Polidea.Software> [image: Twitter]
> <https://twitter.com/polidea> [image: Linkedin]
> <https://www.linkedin.com/company/polidea> [image: Instagram]
> <https://instagram.com/polidea> [image: Behance]
> <https://www.behance.net/polidea>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message