---

name: testing-guidelines description: Rules for when and how to run tests during development

Testing Guidelines

Rules that AI should automatically follow during development.

Backend API Testing

When adding or modifying Backend API:

1. Ensure corresponding test file exists (*_test.go)
2. New APIs must include test cases
3. Run all Go tests:

Copydocker compose exec backend go test ./...

1. All tests must pass before completion

Test File Locations

• Handler tests: internal/handlers/*_test.go
• Service tests: internal/services/*_test.go

---

Frontend Browser Testing

When modifying frontend pages:

1. Use browser_subagent to simulate user behavior on that page
2. Do NOT write JavaScript test code
3. Tests should cover the modified functionality flow

Testing Principles

• Simulate real user actions (click, type, navigate)
• Verify UI state changes
• Verify API call results are reflected in the UI

Example Test Flow

Copy1. Open target page
2. Perform user actions (click buttons, fill forms)
3. Verify page displays correct results
4. Report test results

---

Database Schema Changes

When modifying database schema (add/modify migrations):

1. Reset database
2. Run all API tests (which creates test data)

Copy# 1. Drop and recreate database
docker compose exec postgres psql -U postgres -c "DROP DATABASE IF EXISTS lovelion"
docker compose exec postgres psql -U postgres -c "CREATE DATABASE lovelion"

# 2. Run migrations
docker compose exec backend migrate -path /app/migrations -database "$DATABASE_URL" up

# 3. Run API tests (creates test data)
docker compose exec backend go test ./...

---

Summary Table