gen-tests

/gen-tests — Generate Missing Test Specs

Generate RSpec request specs for untested controllers and service specs for untested services.

Usage

/gen-tests                    # List untested files, prompt for selection
/gen-tests controller         # Generate specs for untested controllers
/gen-tests service            # Generate specs for untested services
/gen-tests path/to/file.rb    # Generate spec for a specific file

Workflow

Step 1: Identify Untested Files

Find controllers/services without corresponding specs:

# Untested controllers
cd server && for f in $(find app/controllers/api/v1 -name '*_controller.rb'); do
  spec="spec/requests/api/v1/$(basename "$f" .rb)_spec.rb"
  [[ ! -f "$spec" ]] && echo "UNTESTED: $f"
done

# Untested services
cd server && for f in $(find app/services -name '*.rb' | grep -v concerns); do
  spec="spec/services/$(echo "$f" | sed 's|app/services/||; s|\.rb$|_spec.rb|')"
  [[ ! -f "$spec" ]] && echo "UNTESTED: $f"
done

Step 2: Read Source & Context

For each file to test, read:

1. The source file itself (understand methods, params, permissions)
2. The routes file (config/routes.rb) for endpoint paths
3. Existing factories in spec/factories/ relevant to the models used
4. Similar existing specs for pattern reference

Step 2b: Query MCP for Test Patterns (if available)

Before generating specs, query MCP for relevant learnings that may improve spec quality:

1. platform.query_learnings — query: "<model/service name> test" (e.g., "ai agent test", "subscription service test")
2. platform.query_learnings — query: "factory <model name>" (e.g., "factory ai_agent", "factory account")

Apply any relevant findings (required factory traits, tricky setup, known assertion patterns) to the spec generation approach.

Graceful degradation: If MCP tools are unavailable or return errors, skip this step and proceed with standard spec generation. MCP is additive, not required.

Step 3: Generate Spec