Test Mocks and Stubs
What you'll learn: How any makes creating test doubles quick and pragmatic when strict typing adds no real safety value.
The Testing Escape Hatch
When writing tests, you often need mock objects or stubs—fake versions of real dependencies that let you isolate the code under test. These test doubles frequently need to satisfy complex interface requirements, but you only care about a few properties or methods for that specific test.
TypeScript's strict typing can become a burden here: if your production code expects an object with 20 properties, but your test only touches 2 of them, you'd have to provide fake values for all 18 unused properties. This creates busywork without improving test reliability.
The any Shortcut
Using any in test code lets you skip the ceremony:
interface UserService {
findById(id: string): Promise<User>;
updateEmail(id: string, email: string): Promise<void>;
deleteAccount(id: string): Promise<boolean>;
validatePassword(id: string, pass: string): boolean;
// ...15 more methods
}
// Without any: tedious stub
const verboseStub: UserService = {
findById: async () => ({ id: '1', name: 'Test' }),
updateEmail: async () => {},
deleteAccount: async () => true,
validatePassword: () => false,
// ...must implement 15 more methods
};
// With any: focused on what matters
const mockService: any = {
findById: async () => ({ id: '1', name: 'Test' })
};
You declare exactly what the test needs, nothing more.
When This Makes Sense
Use any for test doubles when:
- The interface is large but you only exercise a small subset
- The test is isolated and won't leak the mock elsewhere
- Type errors in the mock would be caught immediately at runtime anyway
Key Takeaway: In test code, any streamlines mocking by eliminating irrelevant type obligations, letting you focus on test behavior over compile-time completeness.