ColtenOuO commented on code in PR #75835:
URL: https://github.com/apache/airflow/pull/75835#discussion_r4502757256


##########
contributing-docs/testing/unit_tests.rst:
##########
@@ -139,9 +139,14 @@ test types you want to use in various ``breeze testing`` 
sub-commands in three w
 The defined test types are:
 
 * ``Always`` - Tests that should always be executed (always sub-folder).
-* ``API`` - Tests for the Airflow API (api, api_internal, api_fastapi 
sub-folders).
-* ``CLI`` - Tests for the Airflow CLI (cli folder).
-* ``Core`` - Tests for core Airflow functionality (core, executors, jobs, 
models, ti_deps, utils sub-folders).
+* ``API`` - Tests for the Airflow API (api, api_internal, api_fastapi 
sub-folders), except the ``PublicAPI`` tests.
+* ``PublicAPI`` - Tests for the public REST API routes 
(api_fastapi/core_api/routes/public folder).
+* ``CLI`` - Tests for the Airflow CLI (cli folder), except the ``CLITask`` 
tests.
+* ``CLITask`` - Tests for the ``airflow tasks`` CLI commands 
(cli/commands/test_task_command.py).
+* ``Core`` - Tests for core Airflow functionality (core, executors, jobs, 
ti_deps, utils sub-folders).
+* ``Models`` - Tests for the Airflow models (models folder), except the 
``ModelsTI`` tests.
+* ``ModelsTI`` - Tests for task instances and mapped operators 
(test_cleartasks.py, test_mappedoperator.py
+  and test_taskinstance.py in the models folder).

Review Comment:
   Sure! The key metric was the job's wall-clock time. 
   
   DB tests run each test type serially in its own container, with up to 4 
types in parallel, so a job is as long as its heaviest type. Core, API and CLI 
kept running alone long after the rest of their slice finished, leaving the 
other slots idle. Splitting out their slowest folders lets those parts use the 
idle slots.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to