fix: test discovery and coverage run

Fix test discovery by ignoring the new Test prefixed classes in the
the test model package.

Disable the warning about conflicting includes for pytest coverage,
allowing VS Code to run its pytest coverage command successfully.

Author: stevenh

pydantic_ai_slim/pydantic_ai/models/test.py

@@ -49,6 +49,9 @@ class _WrappedToolOutput:
 class TestToolCallPart:
     """Represents a tool call in the test model."""
 
+    # NOTE: Avoid test discovery by pytest.
+    __test__ = False
+
     call_tools: list[str] | Literal['all'] = 'all'
     deltas: bool = False
 
@@ -57,6 +60,9 @@ class TestToolCallPart:
 class TestTextPart:
     """Represents a text part in the test model."""
 
+    # NOTE: Avoid test discovery by pytest.
+    __test__ = False
+
     text: str
 
 
@@ -68,6 +74,9 @@ class TestTextPart:
 class TestNode:
     """A node in the test model."""
 
+    # NOTE: Avoid test discovery by pytest.
+    __test__ = False
+
     parts: list[TestPart]
     id: str = field(default_factory=_utils.generate_tool_call_id)
 

pyproject.toml

@@ -205,6 +205,8 @@ filterwarnings = [
     # random resource warnings; I suspect these are coming from vendor SDKs when running examples..
     "ignore:unclosed <socket:ResourceWarning",
     "ignore:unclosed event loop:ResourceWarning",
+    # Allow pytest coverage to run without erroring.
+    "ignore:--include is ignored because --source is set:",
 ]
 
 # https://coverage.readthedocs.io/en/latest/config.html#run