Hello everyone,
*TL;DR; The ew shiny and likely much snappier test harness for unit tests is merged to main.* *REQUEST: I have a kind request to committers and contributors - please remember to rebase all the PRs you are merging in the next few days as some of those PRs might break main if not rebased and re-run* As proposed in https://lists.apache.org/thread/bbojb6kqbdvqcshnh80hqw0vhtd6ccwn last week, I have just merged (thanks Vincent for reviews) the PR that **SHOULD** significantly improve speed and stability of our tests (our unit tests should take 30% - 50% percent less time than before - which is huge difference. All that thanks to classifying our tests to two groups : DB and Non-DB tests. There might be some teething problems though so I have a kind request to take a bit more care over the next few days and let me know if you see problems that **could** be related to this change. Regular development is not impacted - you can continue running your tests as you did before, but there is **slight** change for contributing new tests - you might be a bit more careful about side-effects and sometimes you will need to add @pytest.mark.db_test to your tests (but you will get clear errors/link to docs when our CI detects it). I added a bit of context for DB/Non-DB tests in our documentation https://github.com/apache/airflow/blob/main/TESTING.rst#db-and-non-db-tests *DOCS: *The most important (and useful) part of the docs are "Best practices" to follow https://github.com/apache/airflow/blob/main/TESTING.rst#best-practices-for-db-tests when you have problems with marking tests as DB tests. I added some useful examples and guidelines following my experiences when I had to fix some of our tests. Ping me on #development in Slack if you have any questions/problems. I will watch for those to fix them quickly over the next few days; J.
