# Erraggy Oastools Corpus Test

> corpus-test

- Skill: `tomevault-io/erraggy-oastools-corpus-test` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/erraggy-oastools-corpus-test`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/erraggy-oastools-corpus-test/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/erraggy-oastools-corpus-test

---


# corpus-test

Run integration tests against the corpus of real-world OpenAPI specifications.

**Usage:**

- `/corpus-test` — run all corpus tests
- `/corpus-test short` — exclude large specs (faster)

## Step 1: Check Corpus Availability

Use the Glob tool to check for corpus files:

```text
pattern: testdata/corpus/*.{json,yaml,yml}
```

If no corpus files found, download them:

```bash
make corpus-download
```

## Step 2: Run Corpus Tests

Based on the mode argument:

**Full mode** (default):

```bash
make test-corpus
```

**Short mode** (argument = "short"):

```bash
make test-corpus-short
```

Capture and analyze the output.

## Step 3: Analyze Results

> **Note:** Corpus specs are real-world documents (Plaid, DigitalOcean, GitHub, etc.) that often contain validation errors intentionally. Validation failures are expected — the key metric is whether the fixer resolves them.

For each corpus spec, report:

- ✅ Parse/validate/fix succeeded
- ❌ Failures with error details (fixer failed to resolve validation errors)
- ⚠️ New warnings compared to expected behavior

## Step 4: Report

```markdown
## Corpus Test Results

| Spec | Parse | Validate | Fix | Notes |
|------|-------|----------|-----|-------|
| petstore.yaml | ✅ | ✅ | ✅ | |
| github-api.json | ✅ | ❌ | ⚠️ | [details] |
| ... | ... | ... | ... | ... |

### Summary
- **Passed**: N/M specs
- **Failed**: [list]
- **New issues**: [list]
```

## Step 5: Offer Actions

If failures are found:

1. **Investigate** — deep dive into specific failures
2. **Compare with main** — check if failures are regressions
3. **File issues** — create GitHub issues for new failures

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/erraggy) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-13 -->