bifrost-testing

What problem does it solve?

Bifrost development is often slowed by inconsistent test practices, failing or skipped tests, and hard-to-diagnose flaky end-to-end tests that risk shipping broken code to users.

Core Features & Use Cases

• Strict test rule enforcement: Hard non-negotiable rules that ban failing/skipped tests, retries for flaky E2E, and test silencing, ensuring only high-quality test code is committed.
• Standardized test authoring guidelines: Clear, pattern-based rules for writing React component vitest tests, backend pytest unit/e2e tests, and Playwright user journey tests, with reference examples to follow.
• Step-by-step test workflow: Guided process for stack setup, running the correct test commands for your change type, pre-merge regression checks, and optional UX review for new UI features.
• Use Case: A developer adding a new user-facing workflow to Bifrost uses this skill to write the required Playwright happy-path spec, run the full client test suite, and complete the pre-merge checklist before opening a pull request.

Quick Start

Use the bifrost-testing skill to write and run all required tests for your new Bifrost feature, verify all targeted and broader test suites pass, and complete the pre-merge checklist before declaring work done.