Devlog #18: How we test Quedula

We split tests into two layers: unit tests and integration tests.

Unit tests cover business logic in isolation: publication time calculation, parameter validation, error handling. They're fast, deterministic, run on every change.

Integration tests verify component interactions: creating a publication via the API, queuing, status change. They're slower and require a running test database.

One thing we've learned: a test that checks too much at once is fragile. When it fails, it's unclear exactly where things broke. Small focused tests are easier to fix.

Coverage isn't a goal in itself. Tests have value when they catch real regressions.