mik-laj edited a comment on issue #4703: [AIRFLOW-3885] Improve Travis CI cycle time URL: https://github.com/apache/airflow/pull/4703#issuecomment-464107920 > * Make sensible decision about which tests should be ran against multiple database types and which are okay to be tested only once @BasPH It's a brillant idea. Most operators, hooks, etc do not require a database. All operators for GCP also count in this. We can divide the tests into two categories: core and external integration (Not to be confused with integration tests). Dividing will be easy because we look at the structure of directories. Some operators that can not do without a database will be markers as core tests, but it will be information that they are written incorrectly. In the future, we will be able to improve them.. I propose from the creation of the AIrflowTestCase/CoreAirflowTestCase class. CoreAIrflowTestCase will run external integration tests only when the AIRFLOW_TEST_SUBSET environment variable equals to "core". Another idea is to use the decorator, but I think that such a class would be needed anyway. Another idea is to use a decorator, but I think that such a class would be useful anyway. I do not like the idea that every test would have to have a decorator, or run too many times. The idea that all tests have a parent in common sounds logical to me.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
