qa-pwa
Progressive web app testing: service worker lifecycle, Workbox caching strategies, offline fallbacks, web push subscriptions, and the install flow. An authoring agent (pwa-test-author) writes one Playwright spec per PWA surface. Distinct from the cross-channel push harness in qa-notifications.
/plugin install qa-pwa@testland-qaFirst time? Add the marketplace with /plugin marketplace add testland/qa
- Category
- Quality engineering
- Version
v1.3.4- Contents
- 5 skills · 1 agent
- Part of
- qa-role-frontend
Skills5
add-to-homescreen-flow-testsUse when a PWA's manifest, icons or install handler change, install conversions drop, or an install test is flaky.skilloffline-fallback-testsUse when choosing or changing how a PWA route behaves offline, or a 'doesn't work offline' bug needs pinning to a route.skillservice-worker-lifecycle-testsUse when a service worker needs lifecycle tests, users are stuck on an old version after deploy, or caching and offline behavior is untested.skillweb-push-testsUse when a PWA ships browser web push and the subscription lifecycle needs release tests: pushManager.subscribe with VAPID keys, pushsubscriptionchange, push event delivery, push-service responses (201, 410, 413, 429) and unsubscribe.skillworkbox-testsUse when a project uses or is adopting a Workbox service worker and its caching must stay stable across refactors or upgrades: recipe behavior, precache manifest injection, routes, expiration and cacheable-response plugins, workbox-window events, and choosing a cache strategy per route.skill
Agents1
About qa-pwa
Workbox recipes (with cache-strategy design), offline fallback patterns, web-push subscription lifecycle testing, the service-worker state machine plus the general Playwright SW harness, and the single install-flow skill (reference contract + per-PWA suite builder) - the single home for service-worker, install-flow, and cache-strategy testing, distinct from qa-notifications' cross-channel push harness