Creating automated tests for Dust codebases

Write focused, practical tests for the current file following the 80/20 principle.

Instructions

When writing tests for a file:

1. Identify the core functionality: Focus on the most important paths and edge cases that provide 80% of the value
2. Keep it simple: Write straightforward tests that are easy to understand and maintain
3. Minimal mocking:
   • DO NOT mock the database
   • Only mock external services (APIs, third-party services)
   • Prefer real implementations when possible
4. Use factories: Leverage test factories to set up data efficiently
5. Focus on behavior: Test what the code does, not how it does it

For Front (TypeScript/Next.js)