Add agent rules that avoid adding @pytest.mark.asyncio in tests

Signed-off-by: Yuchen Zhang <[email protected]>

Author: yczhang-nv

.coderabbit.yaml

@@ -129,7 +129,7 @@ reviews:
           digit version (ex: `~=1.0`).
         - Not all packages contain Python code, if they do they should also contain their own set of tests, in a
           `tests/` directory at the same level as the `pyproject.toml` file.
-        - When adding a new package, that new package name (as defined in the `pyproject.toml` file) should 
+        - When adding a new package, that new package name (as defined in the `pyproject.toml` file) should
           be added as a dependency to the nvidia-nat-all package in `packages/nvidia_nat_all/pyproject.toml`
 
     - path: "tests/**/*.py"
@@ -142,6 +142,8 @@ reviews:
             @pytest.fixture(name="my_fixture")
             def fixture_my_fixture():
                 pass
+        - Do NOT add `@pytest.mark.asyncio` to any test. Async tests are automatically detected and run by the
+          async runner - the decorator is unnecessary clutter.
 
   auto_apply_labels: true
   suggested_labels: true

.cursor/rules/nat-tests/general.mdc

@@ -26,6 +26,7 @@ All tests in NeMo Agent toolkit use pytest. See the general coding guidelines fo
 - Use `@pytest.fixture(name="fixture_name")` decorator pattern
 - Mock external services with `pytest_httpserver` or `unittest.mock`
 - Maintain ≥ 80% code coverage
+- Do NOT add `@pytest.mark.asyncio` to any test - async tests are automatically detected and run by the async runner
 
 ### Integration Tests
 

.cursor/rules/nat-tests/integration-tests.mdc

@@ -175,6 +175,7 @@ Key practices:
 - Import third-party service libraries at module level in fixtures
 - Use function scope for service fixtures (use session scope)
 - Fail tests when services are unavailable (skip them instead)
+- Add `@pytest.mark.asyncio` decorator - async tests are automatically detected and run by the async runner
 
 ## Running Integration Tests