You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 3af1a3e
Browse filesBrowse the repository at this point in the historyBrowse files
Scope the loop preference to many simple cases and note when
parametrize or separate tests fit better.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Copy file name to clipboardExpand all lines: AGENTS.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,7 +65,7 @@ lives under `pyiceberg/`, organized by concern rather than by engine:
65
65
- Bias towards adding tests to existing files, rather than creating new files.
66
66
- Use existing test fixtures when possible.
67
67
- 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.
68
-
- Prefer a `for` loop in a single test over `@pytest.mark.parametrize`; each parametrized case adds per-test overhead that slows the suite. Include the input in assertion messages so failures are identifiable. Use `parametrize`only when cases need different fixtures (e.g., multiple catalogs).
68
+
- 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.
0 commit comments