Skip to content
Back to skills

Acceptance Tests All

ASecurity

Run all framework acceptance tests. Default is sequential (single `deno task acceptance-tests`). Use `--parallel` for 5-subagent parallel mode. Triggers on "run all acceptance tests", "acceptance-tests all", "/acceptance-tests-all".

  • 3 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 2, 2026
ai-agentsbash

Security analysis

A100/100

Scanned September 2, 2026

npx -y skills add korchasa/flowai --skill acceptance-tests-all --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Acceptance Tests All?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Acceptance Tests All
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/korchasa-acceptance-tests-all/badge)](https://www.skillsdirectory.com/skills/korchasa-acceptance-tests-all)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: acceptance-tests-all
description: Run all framework acceptance tests. Default is sequential (single `deno task acceptance-tests`). Use `--parallel` for 5-subagent parallel mode. Triggers on "run all acceptance tests", "acceptance-tests all", "/acceptance-tests-all".
---

# Run All Acceptance Tests

## Workflow

### 1. Choose mode

- **Default (sequential)**: Run all acceptance tests in a single `deno task acceptance-tests` invocation.
- **Parallel** (when user says "parallel", "fast", or passes `--parallel`): Split across 5 subagents.

### 2a. Sequential mode (default)

Run all acceptance tests in one command:

```bash
deno task acceptance-tests
```

Report results as they appear. After completion, summarize pass/fail counts.

### 2b. Parallel mode

#### Discover scenarios

```bash
deno eval "
import { dirname, join } from '@std/path';
import { existsSync, walk } from '@std/fs';
const fw = join(Deno.cwd(), 'framework');
const ids = [];
for await (const pe of Deno.readDir(fw)) {
  if (!pe.isDirectory) continue;
  const sd = join(fw, pe.name, 'skills');
  if (!existsSync(sd)) continue;
  for await (const e of walk(sd, { maxDepth: 10, includeFiles: true, match: [/mod\.ts$/] })) {
    if (!e.path.includes('/acceptance-tests/') || e.path.includes('/fixture/')) continue;
    try {
      const m = await import('file://' + e.path);
      for (const k in m) { if (m[k]?.id && m[k]?.userQuery) ids.push(m[k].id); }
    } catch {}
  }
}
console.log(JSON.stringify(ids));
"
```

#### Split into 5 batches

Distribute scenarios round-robin across 5 batches.

#### Launch 5 parallel subagents

For each batch N (1-5), launch an `acceptance-test-runner` subagent with this prompt template:

```
Run these acceptance test scenarios sequentially using deno task acceptance-tests.
For each scenario, run: deno task acceptance-tests -f <scenario-id> --lock batch-N.lock
Scenarios: <comma-separated list of IDs in this batch>

IMPORTANT: Always pass --lock batch-N.lock to avoid lock conflicts with other parallel agents.

Run them one by one. After each scenario completes, report its result (PASS/FAIL, errors, warnings).
At the end, provide a summary of all scenarios in this batch.
```

Launch ALL 5 subagents in a SINGLE message (parallel Agent tool calls). Use `run_in_background: true` for each.

#### Status reporting

While subagents are running, report status to the user every ~60 seconds:

- How many subagents have completed vs still running
- Results from completed subagents (if any)

### 3. Final report

After all scenarios complete, compile results into a summary:

```
## Acceptance Test Results

- Total scenarios: N
- Passed: N
- Failed: N
- Errors: N
- Warnings: N

### Failed scenarios
- scenario-id: reason
```

## Important notes

- The `acceptance-test-runner` agent is READ-ONLY. It runs acceptance tests but does not fix anything.
- Each `deno task acceptance-tests -f <id>` runs a single scenario. The `-f` flag filters by substring match, so use exact scenario IDs to avoid matching multiple scenarios.
- Each subagent MUST use `--lock batch-N.lock` (where N is the batch number 1-5) to avoid lock conflicts between parallel agents.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.