Skip to content
Back to skills

Specialist Integration Test Generator

ASecurity

Generates one integration/E2E test from an approved test case spec using existing project patterns. Use for independent Zephyr TC, Playwright, Appium, Flutter, or API test generation.

  • 549 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added June 6, 2026
developmentshellapi

Works with

  • cli
  • api
  • mcp

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 3, 2026

npx -y skills add HoangNguyen0403/agent-skills-standard --skill specialist-integration-test-generator --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Specialist Integration Test Generator?

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

Security grade badge for Specialist Integration Test Generator
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/hoangnguyen0403-specialist-integration-test-generator/badge)](https://www.skillsdirectory.com/skills/hoangnguyen0403-specialist-integration-test-generator)

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: specialist-integration-test-generator
description: Generates one integration/E2E test from an approved test case spec using existing project patterns. Use for independent Zephyr TC, Playwright, Appium, Flutter, or API test generation.
metadata:
  internal: true
  triggers:
    keywords:
      - integration test generator
      - generate E2E test
      - Zephyr TC to test
      - Playwright test
---
# Specialist: Integration Test Generator

## **Priority: P1 (HIGH)**

## Role

Generate one test file or append one scenario from a structured TC/spec while following loaded project skills.

## Budget

- One TC/spec per invocation.
- Read nearest existing test sample before writing.
- Format only changed test file.
- No commit, push, or sub-agents.

## Lane → Driver

| Lane | Driver | Fallback |
| --- | --- | --- |
| `web` | `playwright-cli` | Playwright MCP (no shell); else `Test: BLOCKED (driver)` |
| `ios` / `android` | Appium MCP local | Appium MCP `remoteServerUrl` cloud; else `Test: BLOCKED (driver)` |
| `api` | none | — |

## Steps

1. Load matching project skills for target file type before code.
2. Locate target test folder and nearest sibling sample.
3. Decide append vs new file based on existing structure.
4. For `lane: web`, drive every interaction through the screen's page object and the `pages` fixture per `quality-engineering-playwright-pom-generation`; if the page object is missing, return `Test: BLOCKED` naming it instead of using raw `page`.
5. Implement one scenario asserting the plan's `Expected` with stable selectors/data (web: through page-object state getters); tag it `@AC-n`.
6. Run formatter and the smallest reliable test command.

## Output

```text
Skill loaded: [skills]
TC: [key/name]
Seed: [sample or self-search]
File: [path]
Action: appended | created
Format: CLEAN | BLOCKED
Test: PASS | FAIL | BLOCKED | BLOCKED (driver)
```

## Anti-Patterns

- No writing before skill loading.
- No broad test refactors.
- No unverified helper APIs in suggested code.
- No raw `page.locator` in a web spec when a page object exists or is required.

Files in this skill

  • SKILL.md1.4 KB
  • evals/evals.json665 B

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.