alexion
e684ac481e
Adopt the convention that a Module's option path mirrors its directory under modules/, with an index file naming the directory's own segment. - Group agent Modules under modules.agents.*: claude-code (whole directory), pi (flattened to a file), skills (renamed from agent-skills), and gitea-axi under an agents/tools/ subgroup. The agents/ and tools/ folders are pure namespace prefixes with no aggregator enable. - Nest hypridle and hyprlock under modules.desktop.hyprland.*, with hyprland.nix as the index, and update the desktop aggregator. - Remove the obsolete example Module. - Record the convention in CONTEXT.md and ADR 0004, and update the neogaia host, the two live CLAUDE.md gotchas, and the skills Module's intentional Enable-convention exception comment.
60 lines
1.4 KiB
Markdown
60 lines
1.4 KiB
Markdown
# When to Mock
|
|
|
|
Mock at **system boundaries** only:
|
|
|
|
- External APIs (payment, email, etc.)
|
|
- Databases (sometimes - prefer test DB)
|
|
- Time/randomness
|
|
- File system (sometimes)
|
|
|
|
Don't mock:
|
|
|
|
- Your own classes/modules
|
|
- Internal collaborators
|
|
- Anything you control
|
|
|
|
## Designing for Mockability
|
|
|
|
At system boundaries, design interfaces that are easy to mock:
|
|
|
|
**1. Use dependency injection**
|
|
|
|
Pass external dependencies in rather than creating them internally:
|
|
|
|
```typescript
|
|
// Easy to mock
|
|
function processPayment(order, paymentClient) {
|
|
return paymentClient.charge(order.total);
|
|
}
|
|
|
|
// Hard to mock
|
|
function processPayment(order) {
|
|
const client = new StripeClient(process.env.STRIPE_KEY);
|
|
return client.charge(order.total);
|
|
}
|
|
```
|
|
|
|
**2. Prefer SDK-style interfaces over generic fetchers**
|
|
|
|
Create specific functions for each external operation instead of one generic function with conditional logic:
|
|
|
|
```typescript
|
|
// GOOD: Each function is independently mockable
|
|
const api = {
|
|
getUser: (id) => fetch(`/users/${id}`),
|
|
getOrders: (userId) => fetch(`/users/${userId}/orders`),
|
|
createOrder: (data) => fetch('/orders', { method: 'POST', body: data }),
|
|
};
|
|
|
|
// BAD: Mocking requires conditional logic inside the mock
|
|
const api = {
|
|
fetch: (endpoint, options) => fetch(endpoint, options),
|
|
};
|
|
```
|
|
|
|
The SDK approach means:
|
|
- Each mock returns one specific shape
|
|
- No conditional logic in test setup
|
|
- Easier to see which endpoints a test exercises
|
|
- Type safety per endpoint
|