Spike Curtis 8c8bd3141f chore: stop creating coderd for notification unit tests (#15133) ...

A bunch of notification tests create a whole `coderd`, when all they use is the database and logger.  This makes the tests more expensive to run, and pollutes the test logs with a bunch of stuff that doesn't matter (e.g. tailnet).

2024-10-21 10:39:37 +04:00

..

dispatch

chore(coderd/notifications): expand golden file testing for notifications (#15032)

2024-10-14 12:34:32 +00:00

render

feat: turn off notification via email (#14520)

2024-09-11 11:10:24 -03:00

reports

chore: remove notifications experiment (#14869)

2024-10-01 13:43:47 +00:00

testdata/rendered-templates

feat(site): add forgot password link (#15108)

2024-10-18 09:50:22 -03:00

types

feat: notifications: report failed workspace builds (#14571)

2024-09-18 09:11:44 +02:00

enqueuer.go

feat: notifications: report failed workspace builds (#14571)

2024-09-18 09:11:44 +02:00

events.go

feat: implement api for "forgot password?" flow (#14915)

2024-10-04 11:53:25 +01:00

manager_test.go

chore: stop creating coderd for notification unit tests (#15133)

2024-10-21 10:39:37 +04:00

manager.go

chore: remove notifications experiment (#14869)

2024-10-01 13:43:47 +00:00

metrics_test.go

chore: stop creating coderd for notification unit tests (#15133)

2024-10-21 10:39:37 +04:00

metrics.go

feat: implement observability of notifications subsystem (#13799)

2024-07-11 10:57:49 +02:00

notifications_test.go

chore: stop creating coderd for notification unit tests (#15133)

2024-10-21 10:39:37 +04:00

notifier.go

feat: notifications: report failed workspace builds (#14571)

2024-09-18 09:11:44 +02:00

spec.go

feat: notifications: report failed workspace builds (#14571)

2024-09-18 09:11:44 +02:00

utils_test.go

chore: use idiomatic test setup in notification tests (#14416)

2024-08-23 16:29:27 +02:00