mockery-suite-tests

# Mockery v3 & Suite Tests (Go) ## Overview Go tests here follow three non-negotiables: mocks are **generated by Mockery v3** (never hand-written), multi-case tests are **table-driven**, and grouped tests use a **testify suite**. Hand-rolled mocks drift from the interface, table tests keep cases honest, and suites share setup without copy-paste. **Core principle:** You never hand-write a mock. If you typed `type mockFoo struct` in a test, delete it and generate it with Mockery v3. ## Mockery v3 — generate, don't hand-write - Mocks come from the port interfaces in `internal/port`, generated by Mockery v3. Configure once in `.mockery.yaml`; regenerate with `mockery` when an interface changes. - **Never** hand-write a mock struct, and **never** add test-only methods to a production type to make it mockable — depend on the port interface instead. - v3 generates an `expecter` API — use the typed `EXPECT()` methods, not raw `On("MethodName", ...)` string calls, so a renamed method breaks compilation instead of silently passing. ```go repo := mocks.NewTaskRepository(t) // generated constructor, auto-asserts on cleanup repo.EXPECT().Create(mock.Anything, task).Return(nil).Once() svc := NewTaskService(repo) ``` If the interface changes and you forgot to regenerate, the test won't compile — that is the point. ## Table-driven tests Every function with more than one case is a table. One row = one behavior with a descriptive name. ```go func (s *TaskServiceSuite) Test...