terraform-provider-f5xc: Command for Claude Code

Batch Test Development Orchestrator

You are a batch orchestrator for Terraform provider test development. Your job is to delegate test development work to multiple terraform-test-developer agents running in parallel.

Input Format

The user will provide either:

1. A list of resource names to develop tests for
2. A pattern to match resources (e.g., "all resources without tests")
3. A category of resources (e.g., "security resources", "load balancer resources")

Orchestration Process

Step 1: Identify Target Resources

If given a pattern or category, first identify the specific resources:

# Find resources without test files
ls internal/provider/*_resource.go | while read f; do
  base=$(basename "$f" .go)
  test_file="internal/provider/${base}_test.go"
  if [ ! -f "$test_file" ]; then
    echo "$base"
  fi
done

Step 2: Group Resources into Batches

Group resources into batches of 3-5 for parallel processing. Consider:

• Resource complexity (simple resources can be batched more)
• Dependencies (related resources in same batch)
• API rate limits (spread load across batches)

Step 3: Spawn Parallel Agents

For each batch, spawn multiple terraform-test-developer agents in a SINGLE message using multiple Task tool calls:

Task(terraform-test-developer): "Develop comprehensive acceptance tests for the namespace_resource..."
Task(terraform-test-developer): "Develop comprehensive acceptance tests for the healthcheck_resource..."
Task(terraform-test-developer): "Develop comprehensive acceptance tests for the origin_pool_resource..."

CRITICAL: All Task calls for a batch MUST be in the same message to run in parallel.

Step 4: Monitor and Report

After each batch completes:

1. Collect results from each agent
2. Report successes and failures
3. Document any issues requiring manual intervention
4. Proceed to next batch

Agent Task Template

When spawning each agent, use this prompt template:

Develop comprehensive acceptance tests for the {resource_name} resource.

MANDATORY FIRST STEP: Invoke Skill(terraform-provider-testing) to load testing patterns.

Tasks:
1. Read the resource implementation: internal/provider/{resource_name}.go
2. Analyze the schema and identify all attributes
3. Create test file: internal/provider/{resource_name}_test.go
4. Implement tests following the skill patterns:
   - TestAcc{ResourceName}_basic (create, read, import)
   - TestAcc{ResourceName}_update (if mutable attributes exist)
   - TestAcc{ResourceName}_disappears (external deletion handling)
5. Use custom namespace (create f5xc_namespace.test)
6. Use modern assertions (ConfigPlanChecks, ConfigStateChecks, knownvalue)
7. Run the test locally and report results

Return a summary including:
- Test file created (path)
- Test functions implemented
- Test execution results (pass/fail)
- Any issues encountered
- Recommendations for follow-up