Add backend monitor and notification tests

docs/progress.md

@@ -50,6 +50,12 @@ Implemented alerting management slice:
 - Existing simple alert conditions are shown in friendly language instead of raw condition data.
 - Worker honors alert rule cooldown before opening a new incident for a recently-triggered rule.
 
+Implemented backend test coverage:
+
+- Test fixtures isolate API tests with an in-memory database and authenticated owner override.
+- Website monitor tests cover asset creation, default alert rule creation, TLS config persistence, and disabled default alerts.
+- Notification channel tests verify saved webhook URLs are encrypted and are not returned by create, list, or update responses.
+
 ## Known Gaps
 
 - Credential vault UI and real credential encryption workflows are not complete.
@@ -63,7 +69,7 @@ Implemented alerting management slice:
 - Email/SMTP notifications are not implemented yet.
 - Graphing exists only as placeholders; metric visualization is not implemented.
 - Worker scheduling is simple polling, not a Redis queue yet.
-- Tests are still minimal and need meaningful backend/worker/frontend coverage.
+- Tests still need worker notification delivery, alert evaluation, and frontend coverage.
 - Production deployment hardening is not done.
 
 ## Recommended Next Work
@@ -78,7 +84,7 @@ Implemented alerting management slice:
 8. Add user administration UI.
 9. Add graphs for website response time and monitor status history.
 10. Add richer alert condition editing.
-11. Add backend and worker tests for the website-monitor and notification flows.
+11. Add worker tests for alert evaluation and notification delivery.
 
 ## Operational Notes