Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
vudovn avatar

Webapp Testing

  • 255 installs
  • 8.1k repo stars
  • Updated August 4, 2026
  • vudovn/antigravity-kit

Webapp-testing is an agent skill that runs headless Playwright checks on a URL and returns JSON page health plus optional screenshots.

About

Webapp-testing is an agent skill for solo and indie builders who need fast, repeatable browser verification without wiring a full E2E suite first. It wraps a small Playwright runner that agents can invoke against any URL to confirm the page loads, surface structured health metadata, and optionally capture a screenshot for visual review or regression notes. The workflow assumes Python on the machine and Chromium via Playwright’s install step, which matches how many builders already script local checks from Claude Code, Cursor, or Codex. Use it when you have a dev or staging URL and want JSON the agent can parse—status, timing context, and errors—instead of parsing messy console paste. It complements manual QA and heavier frameworks by giving a lightweight gate you can run after frontend changes, before deploy, or when debugging “works on my machine” issues. It is not a replacement for CI matrices, accessibility audits, or load testing; it is the first browser truth check in minutes.

  • Bundled `playwright_runner.py` returns JSON with URL, timestamp, status, page info, and optional screenshot path
  • Headless Chromium at 1280×720 for consistent solo-builder smoke runs without manual browser babysitting
  • Clear install path when Playwright is missing: pip install playwright and playwright install chromium
  • Screenshots land in the OS temp directory so disk clutter stays low during quick checks
  • Stdout/stderr UTF-8 handling on Windows avoids broken Unicode in agent logs

Webapp Testing by the numbers

  • 255 all-time installs (skills.sh)
  • +2 installs in the week ending Jul 27, 2026 (Skillselion tracking)
  • Ranked #755 of 2,153 Testing & QA skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/vudovn/antigravity-kit --skill webapp-testing

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs255
repo stars8.1k
Security audit2 / 3 scanners passed
Last updatedAugust 4, 2026
Repositoryvudovn/antigravity-kit

What it does

Run headless Playwright smoke checks on a URL and get JSON health plus optional screenshots before you ship or iterate on a web app.

Who is it for?

Developers smoke-testing dev/staging URLs from an agent after UI or routing changes, with minimal setup beyond Python and Playwright.

Skip if: Skip if you need full CI pipelines, cross-browser matrices, authenticated flows, or performance/load benchmarks—use a dedicated E2E or observability stack instead.

When should I use this skill?

You have a web app URL (local or deployed) and need a quick Playwright browser test with JSON results or a screenshot.

What you get

After the run you get structured JSON with page status and metadata (and a screenshot path when requested) so you can fix failures or proceed to deeper tests and deploy.

  • JSON report with page info and health/status fields
  • Optional PNG screenshot path in temp directory
  • Actionable error payload when Playwright is not installed

By the numbers

  • Headless Chromium viewport固定为 1280×720
  • JSON output includes url, timestamp, status, page info, and optional screenshot path
  • Screenshots saved to system temp directory

Files

SKILL.mdMarkdownGitHub ↗

Web App Testing

Discover and test everything. Leave no route untested.

🔧 Runtime Scripts

Execute these for automated browser testing:

ScriptPurposeUsage
scripts/playwright_runner.pyBasic browser testpython scripts/playwright_runner.py https://example.com
With screenshotpython scripts/playwright_runner.py <url> --screenshot
Accessibility checkpython scripts/playwright_runner.py <url> --a11y

Requires: pip install playwright && playwright install chromium

---

1. Deep Audit Approach

Discovery First

TargetHow to Find
RoutesScan app/, pages/, router files
API endpointsGrep for HTTP methods
ComponentsFind component directories
FeaturesRead documentation

Systematic Testing

1. Map - List all routes/APIs 2. Scan - Verify they respond 3. Test - Cover critical paths

---

2. Testing Pyramid for Web

        /\          E2E (Few)
       /  \         Critical user flows
      /----\
     /      \       Integration (Some)
    /--------\      API, data flow
   /          \
  /------------\    Component (Many)
                    Individual UI pieces

---

3. E2E Test Principles

What to Test

PriorityTests
1Happy path user flows
2Authentication flows
3Critical business actions
4Error handling

E2E Best Practices

PracticeWhy
Use data-testidStable selectors
Wait for elementsAvoid flaky tests
Clean stateIndependent tests
Avoid implementation detailsTest user behavior

---

4. Playwright Principles

Core Concepts

ConceptUse
Page Object ModelEncapsulate page logic
FixturesReusable test setup
AssertionsBuilt-in auto-wait
Trace ViewerDebug failures

Configuration

SettingRecommendation
Retries2 on CI
Traceon-first-retry
Screenshotson-failure
Videoretain-on-failure

---

5. Visual Testing

When to Use

ScenarioValue
Design systemHigh
Marketing pagesHigh
Component libraryMedium
Dynamic contentLower

Strategy

  • Baseline screenshots
  • Compare on changes
  • Review visual diffs
  • Update intentional changes

---

6. API Testing Principles

Coverage Areas

AreaTests
Status codes200, 400, 404, 500
Response shapeMatches schema
Error messagesUser-friendly
Edge casesEmpty, large, special chars

---

7. Test Organization

File Structure

tests/
├── e2e/           # Full user flows
├── integration/   # API, data
├── component/     # UI units
└── fixtures/      # Shared data

Naming Convention

PatternExample
Feature-basedlogin.spec.ts
Descriptiveuser-can-checkout.spec.ts

---

8. CI Integration

Pipeline Steps

1. Install dependencies 2. Install browsers 3. Run tests 4. Upload artifacts (traces, screenshots)

Parallelization

StrategyUse
Per filePlaywright default
ShardingLarge suites
WorkersMultiple browsers

---

9. Anti-Patterns

❌ Don't✅ Do
Test implementationTest behavior
Hardcode waitsUse auto-wait
Skip cleanupIsolate tests
Ignore flaky testsFix root cause

---

Remember: E2E tests are expensive. Use them for critical paths only.

Related skills

Forks & variants (1)

Webapp Testing has 1 known copy in the catalog totaling 15 installs. They canonicalize to this original listing.

How it compares

Lightweight Playwright smoke JSON from the agent, not a hosted browser grid or a full Cypress/Playwright test suite in CI.

FAQ

Who is webapp-testing for?

Developers shipping web apps with AI coding agents who want a fast Playwright smoke check without standing up a full test harness first.

When should I use webapp-testing?

Use it in Validate when a prototype URL needs a quick load check; in Build after frontend or routing edits; and in Ship before release or when debugging production-like URLs. Invoke when you have a URL and need JSON the agent can act on.

Is webapp-testing safe to install?

It runs local browser automation and may fetch arbitrary URLs you pass in—review the Security Audits panel on this page and only point it at URLs you trust in dev or staging.

Testing & QAtestingfrontendintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.