testing

Define testing standards for unit, component, and integration tests in Bun environments.

Updated Sep 16, 2025
One-click install
npx skills add https://github.com/mukles/platejs-markdown-converter --skill testing-mukles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/mukles/platejs-markdown-converter/tree/main/.agents/skills/testing
Command: npx skills add https://github.com/mukles/platejs-markdown-converter --skill testing-mukles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Testing discipline and consistency across codebases to improve reliability and maintainability.

Core Features & Use Cases

  • Defines testing buckets: pure unit tests, thin component or hook contract tests, and golden input/output tests.
  • Recommends deterministic, fast tests with explicit assertions and minimal dependencies.
  • Use case: when adding a feature, align tests with the three buckets to ensure coverage and fast feedback.

Quick Start

Write unit tests next to code with deterministic execution and explicit assertions.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I standardize testing across Bun projects for consistent unit and integration tests?

To standardize testing in Bun, define three distinct test buckets: pure unit tests, thin component contract tests, and golden input/output integration tests. This structure ensures fast feedback, explicit assertions, and deterministic execution across your project.

What is the best way to organize test fixtures and assertions for deterministic execution?

Organize test fixtures near your code with minimal dependencies and use explicit assertions. Categorizing tests into pure unit, component contract, and golden input/output buckets ensures deterministic execution and fast feedback.

Can I use this approach to enforce testing standards for both unit and integration tests?

Yes, this approach enforces testing standards across both unit and integration tests in Bun environments. It applies specific rules for pure unit tests, thin component contracts, and golden input/output integration tests to ensure full coverage and fast feedback.

How do I write unit tests next to code with explicit assertions and fast feedback?

Write unit tests next to your code by placing them in defined testing buckets with deterministic execution and explicit assertions. Using minimal dependencies and structured fixtures ensures fast feedback and reliable code validation.

When do I need golden input/output tests versus thin component contract tests?

Use golden input/output tests for validating integration-level data flows, and thin component contract tests for verifying hook or component interfaces. Categorizing tests into these distinct buckets maintains fast feedback and clear coverage boundaries.