Agent skill

testing-strategies

Build confidence with comprehensive CLI testing. Unit tests catch logic bugs with fakes, integration tests verify API contracts, E2E tests validate workflows.

View SKILL.md on GitHub Repository
Stars 1
Forks 2

Install this agent skill to your Project

npx add-skill https://github.com/adaptive-enforcement-lab/claude-skills/tree/main/plugins/build/skills/testing-strategies

SKILL.md

Testing Strategies

When to Use This Skill

A well-tested CLI uses different testing strategies at different levels. This section covers:

  • Unit Testing - Fake clients and interface-based design
  • Integration Testing - envtest and real API servers
  • E2E Testing - Full workflow tests in CI/CD

Implementation

See the full implementation guide in the source documentation.

Key Principles

Practice Description
Interface first Design for testability with interfaces
Table-driven tests Cover edge cases systematically
Parallel tests Use t.Parallel() where safe
Build tags Separate integration tests with //go:build integration
Clean up Always clean up test resources

Test at the right level. Unit tests catch logic bugs. Integration tests catch API issues. E2E tests catch workflow bugs.

Techniques

Overview

A well-tested CLI uses different testing strategies at different levels. This section covers:

  • Unit Testing - Fake clients and interface-based design
  • Integration Testing - envtest and real API servers
  • E2E Testing - Full workflow tests in CI/CD

Testing Pyramid

mermaid
graph TB
    E2E[E2E Tests<br/>Full workflow in real cluster]
    Integration[Integration Tests<br/>Real API server with kind/envtest]
    Unit[Unit Tests<br/>Fake clients and mock interfaces]

    E2E --> Integration --> Unit

    %% Ghostty Hardcore Theme
    style E2E fill:#9e6ffe,color:#1b1d1e
    style Integration fill:#65d9ef,color:#1b1d1e
    style Unit fill:#a7e22e,color:#1b1d1e

Test Organization

text
myctl/
├── cmd/
│   ├── check.go
│   └── check_test.go        # Command tests
├── pkg/
│   ├── k8s/
│   │   ├── client.go
│   │   ├── client_test.go   # Unit tests with fakes
│   │   └── fake_client.go   # Test doubles
│   └── selector/
│       ├── selector.go
│       └── selector_test.go
└── test/
    ├── e2e/                  # E2E tests
    └── fixtures/             # Test resources

Makefile Targets

makefile
.PHONY: test test-unit test-integration test-e2e

test: test-unit

test-unit:
    go test -v -race ./...

test-integration:
    go test -v -tags=integration ./pkg/...

test-e2e:
    ./test/e2e/run.sh

Best Practices

Practice Description
Interface first Design for testability with interfaces
Table-driven tests Cover edge cases systematically
Parallel tests Use t.Parallel() where safe
Build tags Separate integration tests with //go:build integration
Clean up Always clean up test resources

Test at the right level. Unit tests catch logic bugs. Integration tests catch API issues. E2E tests catch workflow bugs.

Examples

See examples.md for code examples.

References

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

adaptive-enforcement-lab/claude-skills

github-token-permissions-overview

Understanding GITHUB_TOKEN scope, default permissions, and implementing least-privilege principle for GitHub Actions workflows.

1 2
Explore
adaptive-enforcement-lab/claude-skills

secure

Find and fix security issues before they become incidents. Vulnerability scanning, SBOM generation, supply chain security, and secure authentication workflows.

1 2
Explore
adaptive-enforcement-lab/claude-skills

complete-workflow-examples

Copy-paste hardened CI/CD workflows with SHA-pinned actions, minimal GITHUB_TOKEN permissions, OIDC authentication, and comprehensive security scanning for GitHub Actions.

1 2
Explore
adaptive-enforcement-lab/claude-skills

ephemeral-runner-patterns

Disposable runner patterns for GitHub Actions. Container-based, VM-based, and ARC deployment strategies with complete state isolation between jobs.

1 2
Explore
adaptive-enforcement-lab/claude-skills

action-pinning-overview

Why pinning GitHub Actions to SHA-256 commits matters for supply chain security. Attack vectors from unpinned actions and comparison of tag vs SHA pinning.

1 2
Explore
adaptive-enforcement-lab/claude-skills

github-actions-security-patterns-hub

Complete security patterns for GitHub Actions covering action pinning, GITHUB_TOKEN permissions, third-party action risks, secret management, and runner security.

1 2
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results