quality-engineer

Own Playwright E2E testing and journey matrices for the bnto codebase.

3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/Develonaut/bnto --skill quality-engineer-develonaut
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quality-engineer
Source: https://github.com/Develonaut/bnto/tree/main/.claude/skills/quality-engineer
Command: npx skills add https://github.com/Develonaut/bnto --skill quality-engineer-develonaut

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quality engineering ownership for the bnto codebase, unifying E2E strategy, journey-based design, and test infrastructure to ensure reliable user journeys.

Core Features & Use Cases

  • Owns E2E testing strategy, Playwright-based browser tests, and journey matrices stored under .claude/journeys/.
  • Maintains shared fixtures, test helpers, and infrastructure guidelines to balance speed and coverage across frontend, WASM engine, and API layers.
  • Enforces the Testing Trophy approach (integration-heavy middle, thin unit tests, and robust static checks) to maximize confidence with minimal test debt.

Quick Start

Identify the current journeys under .claude/journeys/ and align tests, configs, and helpers to implement the Testing Trophy approach.

Frequently Asked Questions about quality-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure end-to-end testing using journey-based design in Playwright?▼

Journey-based design structures end-to-end testing by mapping user journeys into matrices stored under .claude/journeys/, aligning Playwright configs and test helpers to validate frontend, WASM engine, and API layers comprehensively.

What is the Testing Trophy approach and how does it apply to E2E test infrastructure?▼

The Testing Trophy approach balances test infrastructure by emphasizing integration-heavy tests, thin unit tests, and robust static checks to maximize coverage confidence with minimal test debt across frontend and WASM layers.

How do I set up Playwright E2E suites for a codebase with WASM execution?▼

Setting up Playwright E2E suites for WASM execution involves configuring shared fixtures, test helpers, and cross-stack journey matrices that verify frontend interactions, WASM engine execution, and API integration.

Can I use journey matrices to enforce test quality across frontend, engine, and API layers?▼

Yes, journey matrices enforce test quality across frontend, engine, and API layers by applying four-phase verification and shared testing standards that maintain consistency throughout the end-to-end testing infrastructure.

What's the best way to manage shared fixtures and test helpers for cross-stack E2E testing?▼

Managing shared fixtures and test helpers for cross-stack E2E testing requires maintaining centralized infrastructure guidelines that balance execution speed and coverage across frontend, WASM engine, and API components.

When should I avoid integration-heavy testing in favor of other E2E strategies?▼

Integration-heavy testing should be reconsidered when test execution speed becomes critical or when WASM engine components require isolated verification, though the Testing Trophy approach minimizes test debt across most scenarios.