t1k:web:testing:core
| Field | Value |
|---|---|
| Module | testing |
| Version | 1.14.9 |
| Effort | medium |
| Tools | — |
Keywords: a11y, E2E, integration, k6, load, Playwright, testing, unit, visual, Vitest
How to invoke
Section titled “How to invoke”/t1k:web:testing:core[test-type] [target]Web Testing Skill
Section titled “Web Testing Skill”Comprehensive web testing: unit, integration, E2E, load, security, visual regression, accessibility.
Executed by
Section titled “Executed by”Test strategy, writing tests and diagnosing failures stay on a reasoning tier (routing SSOT:
rules/orchestration-rules.md § “Task-Type → Agent Routing”). Only the bundled scripts are
mechanical:
| Step | Agent |
|---|---|
Run scripts/analyze-test-results.js over named Playwright/Vitest/JUnit result files and report the summary | t1k-metrics-reporter — parses result files into a unified summary |
Run scripts/init-playwright.js into a named directory | t1k-fact-fetcher — scaffolds from a fixed template; destination is already named |
Stays reasoning-tier: choosing what to test, root-causing a flaky or failing test, and coverage judgment.
Quick Start
Section titled “Quick Start”bunx vitest run # Unit testsbunx playwright test # E2E testsbunx playwright test --ui # E2E with UIk6 run load-test.js # Load testsbunx @axe-core/cli https://example.com # Accessibilitybunx lighthouse https://example.com # PerformanceTesting Strategy (Choose Your Model)
Section titled “Testing Strategy (Choose Your Model)”| Model | Structure | Best For |
|---|---|---|
| Pyramid | Unit 70% > Integration 20% > E2E 10% | Monoliths |
| Trophy | Integration-heavy | Modern SPAs |
| Honeycomb | Contract-centric | Microservices |
→ ./references/testing-pyramid-strategy.md
Reference Documentation
Section titled “Reference Documentation”Core Testing
Section titled “Core Testing”./references/unit-integration-testing.md- Vitest, browser mode, AAA./references/e2e-testing-playwright.md- Fixtures, sharding, selectors./references/playwright-component-testing.md- CT patterns (production-ready)./references/component-testing.md- React/Vue/Angular patterns./references/interactive-testing-patterns.md- Forms, keyboard nav, drag & drop, hover/modals./references/shadow-dom-testing.md- Shadow DOM & Web Components piercing selectors
Test Infrastructure
Section titled “Test Infrastructure”./references/test-data-management.md- Factories, fixtures, seeding./references/database-testing.md- Testcontainers, transactions./references/ci-cd-testing-workflows.md- GitHub Actions, sharding./references/contract-testing.md- Pact, MSW patterns
Cross-Browser & Mobile
Section titled “Cross-Browser & Mobile”./references/cross-browser-checklist.md- Browser/device matrix./references/mobile-gesture-testing.md- Touch, swipe, orientation
Performance & Quality
Section titled “Performance & Quality”./references/performance-core-web-vitals.md- LCP/CLS/INP, Lighthouse CI./references/visual-regression.md- Screenshot comparison./references/test-flakiness-mitigation.md- Stability strategies
Accessibility & Security
Section titled “Accessibility & Security”./references/accessibility-testing.md- WCAG, axe-core./references/security-testing-overview.md- OWASP Top 10./references/security-checklists.md- Auth, API, headers
API & Load
Section titled “API & Load”./references/api-testing.md- Supertest, GraphQL./references/load-testing-k6.md- k6 patterns
Checklists
Section titled “Checklists”./references/pre-release-checklist.md- Complete release checklist./references/functional-testing-checklist.md- Feature testing
Scripts
Section titled “Scripts”Initialize Playwright Project
Section titled “Initialize Playwright Project”bun ./scripts/init-playwright.js [--ct] [--dir <path>]Creates best-practice Playwright setup: config, fixtures, example tests.
Analyze Test Results
Section titled “Analyze Test Results”bun ./scripts/analyze-test-results.js \ --playwright test-results/results.json \ --vitest coverage/vitest.json \ --output markdownParses Playwright/Vitest/JUnit results into unified summary.
CI/CD Integration
Section titled “CI/CD Integration”Runners: CI test jobs run on our ARC pool, not ubuntu-latest:
runs-on: [self-hosted, arc, the1studio, org] — all four labels, exact and case-sensitive; a
missing org makes the job queue forever with no error. The pool is Linux x64 with Docker-in-Docker
and a 4 GiB per-pod memory ceiling (memory.oom.group=1, measured 2026-08-22), so keep Playwright
--workers modest and shard rather than turning workers up. GitHub-hosted is correct only for a job
that genuinely needs a clean public IP or a non-Linux OS. Runner rule: /t1k:web:devops:core
§ “GitHub Actions Runner”.
jobs: test: runs-on: [self-hosted, arc, the1studio, org] steps: - run: bun run test:unit # Gate 1: Fast fail - run: bun run test:e2e # Gate 2: After unit pass - run: bun run test:a11y # Accessibility - run: bunx lhci autorun # Performance