# Test, Fix, Commit and Push Workflow Execute a complete development workflow that ensures code quality before pushing changes to the remote repository. ## Workflow Steps ### 1. Run All Tests Execute comprehensive testing across the entire project: **Backend Tests:** * Run all Go unit tests: `go test ./...` * Run RADIUS protocol tests: `go test ./internal/radiusd/...` * Run benchmark tests if applicable: `go test -bench=. ./internal/radiusd/` * Check for race conditions: `go test -race ./...` **Frontend Tests:** * Navigate to `web/` directory * Run frontend tests: `npm test` or `npm run test` * Run build validation: `npm run build` to ensure production build succeeds **Integration Tests:** * Verify database migrations work: Check `app.MigrateDB()` functionality * Test RADIUS authentication flow end-to-end if changes affect core services * Validate API endpoints if admin API routes were modified ### 2. Fix Issues If any tests fail: * Analyze the failure output carefully * Trace the root cause through the codebase * Apply fixes following project conventions: * Maintain consistent error handling patterns * Follow existing logging standards (zap with namespace) * Preserve architectural patterns (errgroup for services, app.GDB() for database access) * Update vendor-specific code according to specifications * Re-run ALL tests after each fix * Iterate until all tests pass **Do not proceed to commit until all tests pass successfully.** ### 3. Commit Changes Once all tests pass, commit the changes with proper organization: **Commit Strategy:** * **Small changes (1-5 files):** Single commit * **Large changes:** Categorize into logical batches: * Group by feature/component (e.g., "auth service", "admin API", "frontend UI") * Separate backend and frontend changes * Isolate refactoring from new features * Keep test updates with their corresponding code changes **Commit Message Format:** Follow conventional commits specification: ``` ():