qwik-e2e-verification

Solid

Use when creating, modifying, debugging, or running Qwik Playwright e2e tests under e2e/, including router, adapters, docs, CLI, and React integration suites.

Testing & QA 55 stars 2 forks Updated 5 days ago MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
58
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Qwik E2E Verification Use this skill for Playwright e2e work in `e2e/**`. Keep the repo-wide rules from `.ruler/AGENTS.md` in force. ## Fast Path 1. Identify the suite: Qwik core app, Qwik Router, adapters, docs, CLI, or Qwik React. 2. Run the dev rebuild first when testing Qwik runtime/router behavior. 3. Use the suite's Playwright config and the browser-selection style that config expects. 4. Prefer one focused e2e file before broad suite commands. 5. When debugging app fixtures, inspect the matching `e2e/*/apps/` source before changing tests. 6. Turn a failing behavior into the smallest deterministic regression. Avoid sleeps and broad assertions when a route, marker, event, or serialized state check can prove the behavior. ## Suites - Main Qwik e2e: `e2e/qwik-e2e/tests/` - Router e2e: `e2e/qwik-e2e/tests/qwikrouter/` - Adapter e2e: `e2e/adapters-e2e/tests/` - Docs e2e: `e2e/docs-e2e/tests/` - CLI e2e: `e2e/qwik-cli-e2e/tests/` - React integration e2e: `e2e/qwik-react-e2e/tests/` ## Commands Main Qwik e2e config uses `--browser`, not Playwright projects: ```bash pnpm build.core.dev pnpm playwright test e2e/qwik-e2e/tests/events.e2e.ts --browser=chromium --config e2e/qwik-e2e/playwright.config.ts pnpm playwright test e2e/qwik-e2e/tests/qwikrouter/nav.e2e.ts --browser=chromium --config e2e/qwik-e2e/playwright.config.ts ``` Other suites may use named Playwright projects. Check their config before choosing flags: ```bash pnpm playwright test e2e/docs-e2e/tests/do...

Details

Author
modem-dev
Repository
modem-dev/ossrules
Created
1 weeks ago
Last Updated
5 days ago
Language
Python
License
MIT

Integrates with

Playwright · Testing

Similar Skills

Semantically similar based on skill content — not just same category

Testing & QA Listed

playwright-e2e

Execute QA-approved browser E2E in a run-owned Node Testcontainers environment. Prove the app/baseURL and stateful endpoints are ephemeral, seed synthetic case data, execute once, verify cleanup, teardown with zero orphans, and report evidence. Use after QA hands off UI scenarios or when asked to run Playwright E2E.

1 Updated 5 days ago
ch4570
Testing & QA Listed

playwright-e2e

End-to-end testing and click-verification of web apps with Playwright — install, write specs, drive authenticated pages, take screenshots, and run in CI. Use when verifying a web change actually works in a real browser, testing user flows, debugging a UI bug live, or confirming an authed/gated page before shipping. Keywords Playwright, e2e, browser test, click test, screenshot, headless.

1 Updated 2 days ago
5dive-ai
Testing & QA Listed

vibe-e2e

Generates and runs full end-to-end UI tests using Playwright against a live URL. Auto-installs Playwright and Chromium if not present — isolated in e2e/ folder, never pollutes app dependencies. Reads SPEC.md and FEATURES.md to automatically generate test flows covering every critical user journey. Runs tests with video recording on failure and HTML report. Two-device flows (poster + joiner, sender + receiver) use parallel browser contexts. OAuth flows are skipped with clear warnings. Generates a cleanup script that deletes all test data after the suite runs. e2e: regenerate rewrites all tests from current SPEC.md. Triggers: "e2e: https://url" to run against a live URL, "e2e: regenerate" to rewrite tests from spec.

7 Updated 3 days ago
aakashdhar