IDE Rule: Jest Unit Testing
IDE Rule: Jest 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: Jest 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 | 971 |
| Source file | .cursorrules |
| Access tier | Free public (MIT) |
Pre-Filled Template
---
description: "Cursor rules for Jest development with unit testing."
globs: **/*
alwaysApply: false
---
# Persona
You are an expert developer with deep knowledge of Jest 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
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 jest.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 null values, undefined, and unexpected types
**8** **Test Quantity**: Limit to 3-5 focused tests per file for maintainability
# Example Unit Test
```js
// Mock dependencies before imports
jest.mock('../api/taxRate', () => ({
getTaxRate: jest.fn(() => 0.1), // Mock tax rate as 10%
}));
// Import module under test
const { calculateTotal } = require('../utils/calculateTotal');
describe('calculateTotal', () => {
beforeEach(() => {
jest.clearAllMocks();
});
it('should calculate total for valid items with tax', () => {
// Arrange
const items = [{ price: 10, quantity: 2 }, { price: 20, quantity: 1 }];
// Act
const result = calculateTotal(items);
// Assert
expect(result).toBe(44); // (10 * 2 + 20 * 1) * 1.1 (tax) = 44
});
it('should handle empty array', () => {
const result = calculateTotal([]);
expect(result).toBe(0);
});
it('should throw error for invalid item data', () => {
const items = [{ price: 'invalid', quantity: 1 }];
expect(() => calculateTotal(items)).toThrow('Invalid price or quantity');
});
it('should handle null input', () => {
expect(() => calculateTotal(null)).toThrow('Items must be an array');
});
});
```
# TypeScript Example
```ts
// Mock dependencies before imports
jest.mock('../api/userService', () => ({
fetchUser: jest.fn(),
}));
// Import the mocked module and the function to test
import { fetchUser } from '../api/userService';
import { getUserData } from '../utils/userUtils';
// Define TypeScript interfaces
interface User {
id: number;
name: string;
email: string;
}
describe('getUserData', () => {
beforeEach(() => {
jest.clearAllMocks();
});
it('should return user data when fetch is successful', async () => {
// Arrange
const mockUser: User = { id: 1, name: 'John Doe', email: 'john@example.com' };
(fetchUser as jest.Mock).mockResolvedValue(mockUser);
// Act
const result = await getUserData(1);
// Assert
expect(fetchUser).toHaveBeenCalledWith(1);
expect(result).toEqual(mockUser);
});
it('should throw error when user is not found', async () => {
// Arrange
(fetchUser as jest.Mock).mockResolvedValue(null);
// Act & Assert
await expect(getUserData(999)).rejects.toThrow('User not found');
});
it('should handle API errors gracefully', async () => {
// Arrange
(fetchUser as jest.Mock).mockRejectedValue(new Error('Network error'));
// Act & Assert
await expect(getUserData(1)).rejects.toThrow('Failed to fetch user: Network error');
});
});
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: Jest 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: Jest Unit Testing is a static blueprint with no dynamic variables. Copy it and use it as-is.
Is IDE Rule: Jest Unit Testing free?
Yes. IDE Rule: Jest 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: Jest Unit Testing need?
IDE Rule: Jest Unit Testing is a static blueprint with no dynamic variables. Copy it and use it as-is.