testing-guide

Standardize Vitest-based unit and E2E tests with colocated file conventions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/nixopus/agent --skill testing-guide-nixopus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-guide
Source: https://github.com/nixopus/agent/tree/main/.cursor/skills/testing-guide
Command: npx skills add https://github.com/nixopus/agent --skill testing-guide-nixopus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing and maintaining tests is often inconsistent across a codebase. This Skill provides a centralized guide for Vitest configuration, test file placement, and common testing conventions to improve reliability and onboarding.

Core Features & Use Cases

  • Vitest configuration overview and defaults for unit and E2E tests
  • Guidance on colocated test files alongside source code
  • Examples of mocking patterns, test organization, and naming conventions

Quick Start

Run the test suite locally to verify changes.

Frequently Asked Questions about testing-guide

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

FAQPage Schema
How do I organize Vitest test files alongside my source code?

Colocated Vitest test files are placed alongside source code to improve discoverability and onboarding. Using frontmatter-driven discovery and standardized naming conventions ensures consistent test file placement across the project.

What is the best way to standardize mocking patterns in Vitest?

Standardizing mocking patterns in Vitest involves applying consistent conventions for unit and E2E tests. A centralized guide provides examples of common mocking techniques to ensure reliable test execution within a Node environment.

Can I use this guide for both unit and E2E tests in a Node environment?

Yes, this guide applies to both unit and E2E tests running in a Node environment. It provides Vitest configuration defaults and testing conventions designed to standardize your entire testing workflow across different test types.

How do I configure Vitest defaults for a new project?

Configuring Vitest defaults involves setting up centralized configuration for unit and E2E tests. This guide outlines the standard configuration overview to ensure reliable test execution and consistent onboarding for your team.

Why does my team need a standardized Vitest testing workflow?

A standardized Vitest workflow solves the problem of inconsistent test writing across a codebase. Centralizing configuration, file placement, and mocking patterns improves overall test reliability and accelerates new developer onboarding.