This is an automated email from the ASF dual-hosted git repository. github-merge-queue[bot] pushed a commit to branch gh-readonly-queue/main/pr-4150-5becad1aefcc7de7767d2aa30cef07b48c61aff3 in repository https://gitbox.apache.org/repos/asf/iceberg-python.git
commit a1a43c52cdd4a521378fe7f877658d32b45c2d14 Author: Kevin Liu <[email protected]> AuthorDate: Sun Oct 25 04:04:50 2026 +0000 Prefer for loops over parametrized tests in AGENTS.md (#4150) * Prefer for loops over parametrized tests in AGENTS.md Each parametrized case adds per-item pytest overhead (~0.3ms measured), which slows the suite as cases accumulate. Co-authored-by: Copilot App <[email protected]> * Simplify parametrize guidance in AGENTS.md Scope the loop preference to many simple cases and note when parametrize or separate tests fit better. Co-authored-by: Copilot App <[email protected]> --------- Co-authored-by: Copilot App <[email protected]> --- AGENTS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/AGENTS.md b/AGENTS.md index c13a75c39..3dc1d79c7 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -65,6 +65,7 @@ lives under `pyiceberg/`, organized by concern rather than by engine: - Bias towards adding tests to existing files, rather than creating new files. - Use existing test fixtures when possible. - We have a strong bias towards integration testing over mocks. Mocks should be avoided whenever possible and should only be used if similar, existing tests are using mocks. +- Prefer a `for` loop over `@pytest.mark.parametrize` for many simple cases; each parametrized case adds per-test overhead. Use `parametrize` when cases need different fixtures, and separate tests when cases are complex. ### Required CI and Merge Queue
