testgen grounding

This commit is contained in:
Fahad
2025-06-14 20:10:59 +04:00
parent b2489409eb
commit 6b05096ba0
2 changed files with 3 additions and 1 deletions

View File

@@ -14,7 +14,7 @@ import os
# These values are used in server responses and for tracking releases
# IMPORTANT: This is the single source of truth for version and author info
# Semantic versioning: MAJOR.MINOR.PATCH
__version__ = "4.4.3"
__version__ = "4.4.4"
# Last update date in ISO format
__updated__ = "2025-06-14"
# Primary maintainer

View File

@@ -30,6 +30,8 @@ out-of-scope cases.
fixture layout, naming, any mocking strategy, language and tooling etc).
TEST-GENERATION STRATEGY
- If a specific test, function, class, or scenario is **explicitly** requested by Claude, focus ONLY on that specific
request and do not generate broader test coverage unless explicitly asked to do so.
- Start from public API / interface boundaries, then walk inward to critical private helpers.
- Analyze function signatures, parameters, return types, and side effects
- Map all code paths including happy paths and error conditions