Testing

The testing packages provide facilities for exercising HTTP handlers, whole applications, and JSON responses.

handlertest

handlertest.New(ctx, t, handler) wraps any http.Handler in a fluent request builder. Requests run against httptest with a fresh DI context, so injected dependencies can be set up before each call and shared state is isolated per test:

handlertest.New(ctx, t, handler).
	Get("/users").
	AssertStatusOK()

The builder supports Get, Post, Put, Patch, and Delete, each with a JSON variant that sets Accept/Content-Type headers and encodes the body from a Go value. WithHeader(key, value) adds arbitrary headers.

HttpResult is the fluent assertion result. Status helpers cover exact matches and ranges; body helpers compare decoded JSON, including dotted-path lookups:

handlertest.New(ctx, t, h).
	PostJSON("/users", createUserRequest{Name: "Ada"}).
	AssertStatus(http.StatusCreated).
	AssertJSONContains("user.email", "ada@example.com")

kerneltest

kerneltest.TestKernel[T] boots a real kernel.Kernel with a salusaconfig config and routes requests through k.RootHandler(). Build it once with NewTestKernelFactory(kernel, config) and reuse per test; each call gets a fresh DI context and a bootstrapped kernel:

var newKernel = kerneltest.NewTestKernelFactory(buildKernel(), &config.Config{})

func TestUserGet(t *testing.T) {
	newKernel(t).
		GetJSON("/api/users/1").
		AssertStatus(http.StatusOK).
		AssertJSONContains("name", "Ada")
}

The same fluent verbs as the builder are forwarded: Get, GetJSON, Post, PostJSON, Put, PutJSON, Patch, PatchJSON, Delete, DeleteJSON. Because each call bootstraps the kernel with Bootstrap(ctx), providers and services register fresh for every test.

matches

The matches package defines Matcher and a small set of value matchers such as EqualTo for deferred assertions. It is used where a matcher object is passed rather than a direct comparison; keep in mind the current implementations are early stubs intended to model the pattern.