Document test organization and add Cursor workflow rules.

Record the one-to-one unit test file convention in README and add rules for test placement and copy-ready PR text after first push. Co-authored-by: Cursor <[email protected]>
2026-07-11 10:50:51 +02:00
parent 44b15cb21a
commit a0e5c9dcca
3 changed files with 98 additions and 0 deletions
@@ -174,6 +174,15 @@ uv run pytest -v                                      # full suite (requires Doc

 Integration tests are marked with `@pytest.mark.integration` and require Docker (testcontainers). Backend-specific markers (`needs_redis`, `needs_minio`) let you run only the containers a test module needs. Run unit tests alone for quick local feedback.

+### Test organization
+
+Unit tests live in `tests/unit/` and follow a one-to-one naming convention: `<module>_test.py` tests `python_repositories/<module path>.py`. Examples:
+
+- `json_repository_interface.py` → `tests/unit/json_repository_interface_test.py`
+- `redis_adapter.py` → `tests/unit/redis_adapter_test.py`
+
+Add new tests to the existing file for that module rather than creating cross-cutting test files. Shared fixtures belong in `tests/conftest.py`; module-specific helpers may live in the matching test file.
+
 ### CI base image

 Gitea Actions jobs use a pre-built image (`python-repositories-ci`) with Python 3.12,