refactor-test

Rule: Test Refactoring and Optimization

Goal

To guide an AI assistant in reviewing and improving generated unit tests by optimizing structure, enhancing coverage, removing redundancy, and following testing best practices.

Prerequisites

• Generated unit test file (from generate-unit-test.mdc)
• Original source code file
• Function analysis document (optional but helpful)

Process

1. Analyze Current Tests: Review the existing test file for quality and coverage
2. Identify Improvements: Find areas for optimization, missing coverage, or redundancy
3. Refactor Structure: Optimize test organization and readability
4. Enhance Coverage: Add missing test scenarios
5. Optimize Performance: Improve test efficiency and reliability
6. Update Documentation: Add or improve test comments and descriptions

Analysis Checklist

Test Structure Review

• Are tests logically grouped and organized?
• Are test names descriptive and follow conventions?
• Is there proper setup and teardown?
• Are tests independent of each other?

Coverage Assessment

• Are all code paths tested?
• Are edge cases adequately covered?
• Are error scenarios tested?
• Are async operations properly tested?

Code Quality

• Are there duplicate test patterns that can be abstracted?
• Are mocks properly configured and reset?
• Are test utilities reusable?
• Is the code readable and maintainable?

Performance & Reliability

• Are tests fast and efficient?
• Are there any flaky or unreliable tests?
• Are async operations properly awaited?
• Are timeouts appropriately set?

Refactoring Strategies

1. Test Organization

Before (Poor Organization)

describe('UserService', () => {
  it('should create user', () => { /* test */ });
  it('should handle invalid email in create', () => { /* test */ });
  it('should delete user', () => { /* test */ });
  it('should handle invalid id in delete', () => { /* test */ });
});