Improve cursor rule detail

Author: lchoquel

.cursor/rules/pytest.mdc

@@ -14,7 +14,7 @@ These rules apply when writing unit tests.
     - `tests/unit/` - for unit tests that test individual functions/classes in isolation
     - `tests/integration/` - for integration tests that test component interactions
     - `tests/e2e/` - for end-to-end tests that test complete workflows
-    - `tests/test_pipelines/` - for test pipeline definitions (TOML files)
+    - `tests/test_pipelines/` - for test pipeline definitions (TOML files and their structuring python files)
 - Fixtures are defined in conftest.py modules at different levels of the hierarchy, their scope is handled by pytest
 - Test data is placed inside test_data.py at different levels of the hierarchy, they must be imported with package paths from the root like `tests.pipelex.test_data`. Their content is all constants, regrouped inside classes to keep things tidy.
 - Always put test inside Test classes.