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

Webapp Testing

  • 2 installs
  • 132 repo stars
  • Updated January 14, 2026
  • xenitv1/antigravity-workflows

Guides web app E2E and API testing with Playwright, route discovery, visual testing, and CI integration, plus a Playwright runner script.

About

A web-app testing methodology covering route discovery, Playwright E2E tests, visual and API testing, and CI integration. A developer uses it to systematically test all routes and critical flows of a web application.

  • Route/API discovery then E2E testing with Playwright
  • Bundled playwright_runner.py for browser tests, screenshots, and a11y checks

Webapp Testing by the numbers

  • 2 all-time installs (skills.sh)
  • Ranked #1,683 of 2,153 Testing & QA skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/xenitv1/antigravity-workflows --skill webapp-testing

Add your badge

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

Listed on Skillselion
Installs2
repo stars132
Last updatedJanuary 14, 2026
Repositoryxenitv1/antigravity-workflows

What it does

Guides web app E2E and API testing with Playwright, route discovery, visual testing, and CI integration, plus a Playwright runner script.

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

This week in AI coding

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

unsubscribe anytime.