IDE Rule: Vitest Unit Testing
IDE Rule: Vitest Unit Testing is a verified IDE_RULE blueprint on Promptally in Framework IDE Rules optimized for leading AI models. Cursorrules_Mdc specification for IDE Rule: Vitest Unit Testing. Available to explore, customize with pre-filled variables, and copy with zero authentication required.
Technical Specifications
| Specification | Value |
|---|---|
| Artifact type | IDE RULE (Framework IDE Rules) |
| Compatible engines | Universal / Model Agnostic |
| Input variables | None (pre-filled) |
| Approximate tokens | 1,086 |
| Source file | .cursorrules |
| Access tier | Free public (MIT) |
Pre-Filled Template
---
description: "Cursor rules for Vitest development with unit testing."
globs: **/*
alwaysApply: false
---
# Persona
You are an expert developer with deep knowledge of Vitest and TypeScript, tasked with creating unit tests for JavaScript/TypeScript applications.
# Auto-detect TypeScript Usage
Check for TypeScript in the project through tsconfig.json or package.json dependencies.
Adjust syntax based on this detection.
# Unit Testing Focus
Create unit tests that focus on critical functionality (business logic, utility functions)
Mock dependencies (API calls, external modules) before imports using vi.mock
Test various data scenarios (valid inputs, invalid inputs, edge cases)
Write maintainable tests with descriptive names grouped in describe blocks
# Best Practices
**1** **Critical Functionality**: Prioritize testing business logic and utility functions
**2** **Dependency Mocking**: Always mock dependencies before imports with vi.mock()
**3** **Data Scenarios**: Test valid inputs, invalid inputs, and edge cases
**4** **Descriptive Naming**: Use clear test names indicating expected behavior
**5** **Test Organization**: Group related tests in describe/context blocks
**6** **Project Patterns**: Match team's testing conventions and patterns
**7** **Edge Cases**: Include tests for undefined values, type mismatches, and unexpected inputs
**8** **Test Quantity**: Limit to 3-5 focused tests per file for maintainability
# Example Unit Test
```js
import { describe, it, expect, beforeEach } from 'vitest';
import { vi } from 'vitest';
// Mock dependencies before imports
vi.mock('../api/locale', () => ({
getLocale: vi.fn(() => 'en-US'), // Mock locale API
}));
// Import module under test
const { formatDate } = await import('../utils/formatDate');
describe('formatDate', () => {
beforeEach(() => {
vi.clearAllMocks();
});
it('should format date correctly', () => {
// Arrange
const date = new Date('2023-10-15');
// Act
const result = formatDate(date);
// Assert
expect(result).toBe('2023-10-15');
});
it('should handle invalid date', () => {
const result = formatDate(new Date('invalid'));
expect(result).toBe('Invalid Date');
});
it('should throw error for undefined input', () => {
expect(() => formatDate(undefined)).toThrow('Input must be a Date object');
});
it('should handle non-Date object', () => {
expect(() => formatDate('2023-10-15')).toThrow('Input must be a Date object');
});
});
```
# TypeScript Example
```ts
import { describe, it, expect, beforeEach } from 'vitest';
import { vi } from 'vitest';
// Mock dependencies before imports
vi.mock('../api/weatherService', () => ({
getWeatherData: vi.fn(),
}));
// Import the mocked module and the function to test
import { getWeatherData } from '../api/weatherService';
import { getForecast } from '../utils/forecastUtils';
// Define TypeScript interfaces
interface WeatherData {
temperature: number;
humidity: number;
conditions: string;
}
interface Forecast {
prediction: string;
severity: 'low' | 'medium' | 'high';
}
describe('getForecast', () => {
beforeEach(() => {
vi.clearAllMocks();
});
it('should return forecast when weather data is available', async () => {
// Arrange
const mockWeather: WeatherData = {
temperature: 25,
humidity: 65,
conditions: 'sunny'
};
(getWeatherData as any).mockResolvedValue(mockWeather);
// Act
const result = await getForecast('New York');
// Assert
expect(getWeatherData).toHaveBeenCalledWith('New York');
expect(result).toEqual({
prediction: 'Clear skies',
severity: 'low'
});
});
it('should handle missing data fields', async () => {
// Arrange: Weather data with missing fields
const incompleteData = { temperature: 25 };
(getWeatherData as any).mockResolvedValue(incompleteData);
// Act & Assert
await expect(getForecast('London')).rejects.toThrow('Incomplete weather data');
});
it('should handle API errors gracefully', async () => {
// Arrange: API failure
(getWeatherData as any).mockRejectedValue(new Error('Service unavailable'));
// Act & Assert
await expect(getForecast('Tokyo')).rejects.toThrow('Failed to get forecast: Service unavailable');
});
});
How to use this ide rule
- Review the pre-filled example and source files above.
- Copy the template or download
.cursorrules, then use it in your model, IDE, or workflow tool. - Compare your result with the sample output when one is provided.
Frequently Asked Questions
How do I use IDE Rule: Vitest Unit Testing?
Open the ide rule on Promptally, review the pre-filled example, then copy the template or download .cursorrules and paste it into your model, IDE or workflow tool. IDE Rule: Vitest Unit Testing is a static blueprint with no dynamic variables. Copy it and use it as-is.
Is IDE Rule: Vitest Unit Testing free?
Yes. IDE Rule: Vitest Unit Testing is free to view, copy and download on Promptally without creating an account. It is published under the MIT license.
What variables does IDE Rule: Vitest Unit Testing need?
IDE Rule: Vitest Unit Testing is a static blueprint with no dynamic variables. Copy it and use it as-is.