testing

Organize and standardize Vitest-based testing workflows across web, library, and desktop projects.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/Staysr/lobe-windos-build --skill testing-staysr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/Staysr/lobe-windos-build/tree/main/.agents/skills/testing
Command: npx skills add https://github.com/Staysr/lobe-windos-build --skill testing-staysr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Organizes and standardizes Vitest-based testing workflows across web applications, libraries, and desktop components to improve reliability and maintainability of tests.

Core Features & Use Cases

  • Guided test patterns: standardized describe/it blocks, beforeEach/afterEach hooks, and mocked dependencies for Vitest.
  • Cross-context workflows: templates and examples for Webapp, Packages, and Desktop tests, including setup, mocks, and validation.
  • Rapid-start templates: ready-to-copy test skeletons for common modules to accelerate development and ensure consistency.

Quick Start

Run vitest to execute tests and begin improving coverage in your project.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I structure Vitest unit tests for web, library, and desktop projects?

Vitest test structure for web, library, and desktop projects is standardized using describe/it blocks, beforeEach/afterEach hooks, and mocked dependencies to ensure test isolation across multiple packages.

What is the best way to mock dependencies in Vitest?

Mocking dependencies in Vitest is handled through standardized test setup workflows that organize mocked modules across web, library, and desktop contexts to ensure error handling and test isolation.

How do I set up a Vitest testing workflow across multiple packages?

Setting up a Vitest workflow across multiple packages involves specifying tooling, test setup, and practice templates for each context to standardize writing, debugging, and maintaining tests.

Can I use rapid-start templates for common Vitest test modules?

Rapid-start templates for common Vitest modules provide ready-to-copy test skeletons that accelerate development and ensure consistency for test files, setup, and mocking strategies.

Why does my Vitest test suite need standardized hooks and practices?

Vitest test suites need standardized beforeEach/afterEach hooks and practices to organize test files, maintain error handling, and guarantee test isolation across different project types.

Does TypeScript work with these Vitest testing workflows?

TypeScript works with these Vitest testing workflows, which organize and standardize test structure, setup, and mocking strategies across TypeScript web, library, and desktop projects.