generate-tests

Generate Tests

Generate unit and integration tests following project conventions. Analyzes the target code, identifies test scenarios, and scaffolds test classes with proper mocking and assertions.

Arguments

• {target} -- Handler, entity, or class name to test (e.g., CreateOrderHandler, Order, OrderEndpoints)
• {service} -- Target microservice (optional, auto-detected from file location)
• --integration -- Also generate integration tests with Testcontainers
• --coverage -- Generate tests for all untested handlers in a service

Configuration

Read cloudstack.json from the project root at the start of execution. Extract:

• NAMESPACE = project.namespace (default: detect from *.sln)
• SERVICES = backend.services[] (default: discover from project structure)
• SOLUTION = backend.solutionPath (default: find *.sln)
• MESSAGING = backend.messaging (default: wolverinefx)
• RESULT_PATTERN = backend.resultPattern (default: true)

If cloudstack.json does not exist, auto-detect by scanning the project structure.

Process

Step 1: Locate the target

# Find the file containing the target class
grep -rl "class {target}" src/ --include="*.cs" | head -5

Read the target file completely. Identify:

• Is it a command handler? (method returns Result<T>, takes a command record)
• Is it a query handler? (method returns Result<T>, takes a query record)
• Is it an entity? (inherits from Entity<TId> or AggregateRoot<TId>)
• Is it an event handler? (handles domain/integration events)
• Is it an endpoint? (static class with MapEndpoints)

Step 2: Analyze dependencies

Read the constructor to find injected dependencies:

grep -A 20 "class {target}" <file> | grep -E "private readonly|ILogger|I[A-Z]"

For each dependency, determine:

• Repository interfaces → mock with NSubstitute
• External services → mock with NSubstitute
• ILogger → mock or use NullLogger
• DbContext → use in-memory for unit, Testcontainers for integration