---
name: connector-test
description: Steps 6-8 of the connector workflow. Set up action tracking, test every action against the real API for every auth type, and verify 100% coverage before the connector is considered done.
triggers:
  - /connector-test
  - test [provider] connector
  - run connector actions
  - verify connector works
argument-hint: <provider>
---

# Test a connector

Provider: `$ARGUMENTS`

Covers steps 6-8 of the workflow in `AGENTS.md`. The connector must already validate.

## Load these skills

- `test-connector` (`.claude/skills/test-connector/SKILL.md`) — systematic testing workflow and tracking file
- `test-mcp-connector` (`.claude/skills/test-mcp-connector/SKILL.md`) — only when testing via MCP rather than the CLI

Use the `Skill` tool where available, otherwise read the paths above.

## Before starting

**Ask whether testing should be read-only** (list and get) **or include mutating actions** (create, update, delete). Do not assume mutation is acceptable.

## Order

1. **Create the tracking file** at `.connector-dev/<provider>/testing/actions_tracking.json` before any test runs. `total_required_tests = actions x auth_types`.
2. **Test in dependency order**: list, then get using ids from list, then create, then update, then delete. Never use invented ids.
3. **Update tracking after each test**, recording status per auth type. Mark an action tested only when every auth type has passed.
4. **Leave no trace.** Clean up anything created, and revert any configuration change immediately.

## Done when

- `percentage_complete` is 100 with zero actions left untested
- No failed results remain for any auth type
- Test data created along the way has been removed

Partial coverage is not done. Report the actual numbers from the tracking file rather than a summary impression.