home / Testing & QA / Awt E2E Testing Skill by @sickn33

Awt E2E Testing Skill by @sickn33

FREE

github stars★ 48,690updatedOct 2026repo@sickn33

activity (commits, last 6 months)

6mo ago0

this month2

$git clone https://github.com/sickn33/agentic-awesome-skills

The skill is the skills/awt-e2e-testing folder inside that repository. Copy it into the folder your agent loads skills from; check your agent's documentation for where that is.

about Awt E2E Testing Skill by @sickn33

AI-powered E2E web testing — eyes and hands for AI coding tools.

our take

AI-assisted end-to-end web testing driven by declarative YAML scenarios, executed with Playwright and visual matching using OpenCV and OCR, with platform auto-detection for frameworks such as Flutter, React and Vue.

when to use it

You want scenario-based E2E tests described in YAML
You need visual matching for UI that is hard to select
You test across several frontend frameworks

before you install

Relies on an upstream tool, so read its execution boundary section first
Visual matching can be brittle across screen sizes and themes

what's inside

The original SKILL.md is organised into these sections:

When to Use
Upstream Advertised Capabilities
Execution Boundary
Links
Example
Limitations

source and license

Written and maintained by @sickn33. It is published under the MIT license, which allows reuse with attribution. SkillDirectory does not claim authorship: this page adds our own review and links back to the original, and the skill's text belongs to its author.

View the full SKILL.md on GitHub ↗

Read the opening of the original SKILL.md

# AWT — AI-Powered E2E Testing (Beta)

> `npx skills add ksgisang/awt-skill --skill awt -g`

AWT gives AI coding tools the ability to see and interact with web applications through a real browser. Your AI designs YAML test scenarios; AWT executes them with Playwright.

## When to Use
- You need AI-assisted end-to-end testing through a real browser with declarative YAML scenarios.
- The test flow depends on visual matching, OCR, or platform auto-detection instead of stable DOM selectors.
- You want an E2E toolchain that can both execute tests and explain failures for AI coding workflows.

## Upstream Advertised Capabilities
- YAML scenarios → Playwright with human-like interaction
- Visual matching: OpenCV template + OCR (no CSS selectors needed)
- Platform auto-detection: Flutter, React, Next.js, Vue, Angular, Svelte
- Structured failure diagnosis with investigation checklists
- Learning DB: failure→fix patterns in SQLite
- 5 AI providers: Claude, OpenAI, Gemini, DeepSeek, Ollama
…

Excerpt only, quoted from the author's repository. Open the repository for the complete file.

↓ download .zip