How would you set up a testing strategy for a fullstack Go backend with React frontend?

Question

Accepted Answer

Unit tests: pure functions, domain logic, error handling — fast, no I/O, run on every commit Integration tests: repository + real DB (testcontainers), service + message queue — run on PR API contract tests: HTTP handlers with httptest.NewServer + real DB — verify request/response shapes E2E tests: Playwright/Cypress against a deployed staging environment — run before production deploy Race detector: go test -race in CI catches data races missed by functional tests func TestGetUserHandler(t *testing.T) {
    // Real service and DB
    db := setupTestDB(t)
    repo := NewPostgresUserRepo(db)
    svc := NewUserService(repo)
    handler := NewUserHandler(svc)

// Seed test data
    seedUser(t, db, &User{ID: "123", Name: "Alice"})

// Create test server
    srv := httptest.NewServer(handler.Routes())
    defer srv.Close()

// Make request
    resp, err := http.Get(srv.URL + "/users/123")
    if err != nil { t.Fatal(err) }
    defer resp.Body.Close()

if resp.StatusCode != http.StatusOK {
        t.Errorf("want 200, got %d", resp.StatusCode)
    }

var user User
    json.NewDecoder(resp.Body).Decode(&user)
    if user.Name != "Alice" {
        t.Errorf("want Alice, got %s", user.Name)
    }
}

// OpenAPI contract test
// Use schemathesis or go-openapi-validate to validate
// responses against your OpenAPI spec automatically

How would you set up a testing strategy for a fullstack Go backend with React frontend?

Layer tests by cost and speed: unit tests for domain logic, integration tests for DB and services, contract tests for HTTP API, and E2E tests for critical user flows using Playwright.

How would you set up a testing strategy for a fullstack Go backend with React frontend?

Layer tests by cost and speed: unit tests for domain logic, integration tests for DB and services, contract tests for HTTP API, and E2E tests for critical user flows using Playwright.

Scenario Questions

Follow-up Questions