Honestly having played around with python-based testing in this PR (https://github.com/apache/airflow/pull/11693) I’m in love. It’s so much easier to use than helm-unittest, much more flexible in what we can test for (as we can now use the full python language), and ties in much nicer to our existing CI. Once this PR is merged I hope to phase out helm-unittest and have all helm testing done in this manner. Thank you for pushing this Kamil, this was a great idea :).
via Newton Mail [https://cloudmagic.com/k/d/mailapp?ct=dx&cv=10.0.51&pv=10.15.6&source=email_footer_2] On Sat, Oct 24, 2020 at 1:25 AM, Jarek Potiuk <[email protected]> wrote: Yep. It's much nicer :). Nothing more to add. On Sat, Oct 24, 2020 at 4:54 AM Kamil Breguła < [email protected] [[email protected]] > wrote: Hello, I want to highlight the change we are talking about on Github. It does not significantly impact Apache Airflow, but I think it is a significant change in one of our "sub-projects" - Helm Chart for Apache Airflow. https://github.com/apache/airflow/issues/11657 [https://github.com/apache/airflow/issues/11657] In this change, I proposed migrating from unit tests written in YAML using helm-unittest ( https://github.com/lrills/helm-unittest [https://github.com/lrills/helm-unittest] ) to tests written in Python and run using Pytest. This will allow us to write tests much more conveniently, faster, and it will be much more flexible. I am sending this message to notify all community members about this discussion and leave a mark on the mailing list. What do you think about these proposals? Does anyone have an alternative solution worth considering? Best regardrs, Kamil Breguła -- Jarek Potiuk Polidea [https://www.polidea.com/] | Principal Software Engineer M: +48 660 796 129 [tel:+48660796129] [https://www.polidea.com/]
