skills.rest
verivend
verivendOFFICIAL
Explore all skills by this author →
Website𝕏@verivendGitHub

testing-philosophy

Guide developers in choosing Storybook or Vitest based on code type and complexity.

Updated Mar 10, 2026
Search Tags:#vitest#testing#unit testing#storybook#component testing#developer guide
One-click install
npx skills add https://github.com/verivend/verivend-vue3-template --skill testing-philosophy-verivend
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-philosophy
Source: https://github.com/verivend/verivend-vue3-template/tree/main/.claude/skills/testing-philosophy
Command: npx skills add https://github.com/verivend/verivend-vue3-template --skill testing-philosophy-verivend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a clear decision-making framework to select the most appropriate testing strategy (Storybook or Vitest) for different types of code, ensuring efficient and effective testing practices.

Core Features & Use Cases

  • Guided Decision Making: Offers a clear hierarchy and decision tree for choosing between Storybook and Vitest.
  • Best Practice Guidance: Details when to use each testing tool and provides interaction best practices.
  • Use Case: When you're unsure whether to write unit tests for a new composable function or test a UI component, consult this Skill to determine the optimal approach.

Quick Start

Use the testing-philosophy skill to understand when to use Storybook versus Vitest for testing components and logic.

Frequently Asked Questions about testing-philosophy

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

FAQPage Schema
When should I use Storybook vs Vitest for component testing?▼

Use Storybook for UI component testing to visualize states, and Vitest for non-UI logic. This component testing strategy prioritizes Storybook for visual elements and Vitest for isolated logic validation.

How do I choose the right unit testing strategy for new code?▼

Follow a decision tree that classifies code type and complexity. The unit testing strategy prioritizes Storybook for UI components and Vitest for non-UI logic, ensuring efficient targeted workflows.

What is the best way to test UI components and interaction logic?▼

The best way to test interaction logic is using Storybook for component testing and Vitest for underlying logic. Best practices include isolating non-UI logic to ensure efficient and effective testing.

Can I use Vitest for UI component testing instead of Storybook?▼

While possible, the recommended component testing strategy prioritizes Storybook for UI components. Vitest is better suited for non-UI logic, offering a clear decision tree for optimal tool selection.

Does this testing strategy work for complex composable functions?▼

Yes, for complex composable functions the testing strategy recommends Vitest. It provides a clear hierarchy to determine the optimal approach, directing non-UI logic away from Storybook component testing.

Related Skills

Explore More Software Engineering Skills→
vecearvecear

storybook-setup

Automate Storybook setup, configuration, and CSF3 story authoring for frontend projects.

Community
Intermediate
wtthorntonwtthornton
4

tester

Generate and run Python and JavaScript unit and integration tests with pytest, unittest, and jest, reporting coverage.

Community
Advanced
lsst-sqrelsst-sqre
2

testing-infrastructure

Configure Vitest, React Testing Library, and MSW mocks for monorepo CI testing.

Official
Intermediate
forranyforrany

tdd-workflow

Enforce test-driven development workflows requiring tests before code across unit, integration, and E2E suites with minimum 80% coverage targets.

Community
Intermediate