potiuk commented on code in PR #62928: URL: https://github.com/apache/airflow/pull/62928#discussion_r2889988243
########## AGENTS.md: ########## @@ -77,6 +77,7 @@ UV workspace monorepo. Key paths: - Use `@pytest.mark.parametrize` for multiple similar inputs. - Test fixtures: `devel-common/src/tests_common/pytest_plugin.py`. - Test location mirrors source: `airflow/cli/cli_parser.py` → `tests/cli/test_cli_parser.py`. +- When you run tests during development us the pattern 'cd <distribution where pyproject.toml is located> && uv run pytest <relative path>' to ensure the correct environment and dependencies are used. Review Comment: But those are different things. With uv and `uv run` you actually test if the tests are run fine in isolation from the other modules. When you do `cd project; uv run pytest` - uv will automatically sync the dependencies of the module being tested. This is does not happen when you use `breeze` - breeze will always run tests in the contex of `whole project` when you pass it single test. I think breeze is great before pushing, but for development it's better - in vast majority of cases - to use `uv run`. Maybe I can update also those other instructions - let me see. -- 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]
