test-suite-setup

# Test Suite Setup Skill

Help set up test validation for any project to enable closed-loop workflows.

## When to Use

- Setting up validation commands for a new project
- Discovering existing test infrastructure
- Creating a validation stack for CI/CD or agentic workflows
- Standardizing test commands across a codebase

## Setup Workflow

### Step 1: Detect Project Type

Look for configuration files to identify the stack:

| File | Project Type |
| --- | --- |
| `package.json` | Node.js / TypeScript |
| `pyproject.toml` | Python (modern) |
| `requirements.txt` | Python (pip) |
| `go.mod` | Go |
| `Cargo.toml` | Rust |
| `pom.xml` | Java (Maven) |
| `build.gradle` | Java (Gradle) |

### Step 2: Identify Existing Test Infrastructure

Check for test directories and configurations:

```bash
# Common test locations
ls -la tests/ test/ __tests__/ spec/

# Check for test config files
ls -la pytest.ini jest.config.* vitest.config.* .mocharc.*
```

### Step 3: Extract Available Commands

For Node.js projects:

```bash
# Show available npm scripts
cat package.json | grep -A 30 '"scripts"'
```

For Python projects:

```bash
# Check pyproject.toml for tools
cat pyproject.toml | grep -A 10 '\[tool\.'
```

### Step 4: Generate Validation Commands

Create a validation stack appropriate for the project:

**Template:**

```markdown
## Validation Commands

Execute every command to validate with 100% confidence

- `[lint command]` - Code style and syntax
- `[type check command]` - Type safety (if applicable)
- `[test command]` - Behavior correctness
- `[build command]` - Production readiness
```

## Quick Reference by Stack

### Python (uv + pytest)

```markdown
## Validation Commands

- `uv run ruff check .` - Linting
- `uv run mypy .` - Type checking
- `uv run pytest -v` - Tests
```

### Python (pip + pytest)

```markdown
## Validation Commands

- `flake8 .` or `ruff check .` - Linting
- `mypy .` - Type checking
- `pytest -v` - Tests
```

### TypeScript/JavaScript (npm)

```markdo