jason810496 commented on code in PR #75835: URL: https://github.com/apache/airflow/pull/75835#discussion_r4502170070
########## 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: May I ask what is the thinking process of separating into these more granular modules? e.g. Based on the time spent on each subfolders? Or what is the key metrics for the proposed structure? I'm not against of the proposed structure. Just wonder if there's any better way to parallelize them? -- 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]
