Integration Tests

Integration tests verify behavior that cannot be trusted from isolated unit tests.

Use them for generated wiring, database behavior, backend drivers, runtime boundaries, and rendered App behavior.

Command

GoForj Apps can use normal Go integration tags:

go test -tags=integration ./...

Expected result: integration-tagged packages report ok. If a selected package needs Docker, an emulator, or credentials, state that prerequisite in the test and run its focused package command rather than making the default App suite depend on it.

Framework contributors often run focused integration packages from the goforj repository:

GOCACHE=/tmp/gocache GOMODCACHE=/tmp/gomodcache go test -tags=integration ./internal/forj -count=1

What Belongs Here

Integration tests are a good fit for:

• database connections
• migrations
• generated accessors
• HTTP server bootstrap
• readiness with real dependencies
• backend queue drivers
• distributed event drivers
• storage backends
• rendered App smoke behavior

Testcontainers

GoForj uses testcontainers for backend integration where appropriate.

Keep container-backed tests clearly marked and avoid making ordinary unit tests depend on Docker or network access.

Environment

Integration tests should set required environment explicitly.

Avoid depending on a developer's local .env unless the test is intentionally validating rendered App behavior from that file.

Next Steps

• Rendered App Smoke Tests covers template confidence.
• Database Connections explains connection generation.
• Testing explains how to choose a test layer.