Files
david bb6be245b7
Release / release (push) Failing after 9s
Build CI Images / build-ci-base (push) Failing after 18s
feat: Implement tournament schedule tab and fix E2E tests (#27)
## Summary

This PR implements the tournament schedule tab functionality and fixes all remaining E2E test failures.

### Changes Included

1. **Tournament Schedule Feature**
   - Added tournament schedule page at `/admin/tournaments/[id]/schedule`
   - Implemented "Generate Schedule" button functionality
   - Added schedule generation logic for round-robin tournaments

2. **E2E Test Fixes**
   - Fixed database connection issues in production builds
   - Improved test reliability with better error handling and debugging
   - Updated test infrastructure to use environment variables instead of hardcoded values

3. **CI/CD Updates**
   - Added E2E test job to PR workflow
   - Configured tests to run against development database
   - Moved database password to Gitea secrets

4. **Code Quality**
   - Removed hardcoded passwords from codebase
   - Improved Prisma client configuration
   - Enhanced authentication and navigation components

### Test Results
All 16 E2E test scenarios are now passing:
- Authentication tests: 
- Registration tests: 
- Tournament schedule tests: 
- Player schedule tests: 
- Admin navigation tests: 

### Database Configuration
- Tests run against `euchre_camp_dev` database
- Production builds use environment variables for database configuration
- Database password stored in Gitea secrets as `DB_PASSWORD`

### CI Pipeline
The PR workflow now includes:
1. Unit tests
2. E2E tests (using production build)
3. Version bump analysis

E2E tests must pass before PR can be merged.

Reviewed-on: #27
Co-authored-by: David Gwilliam <dhgwilliam@gmail.com>
Co-committed-by: David Gwilliam <dhgwilliam@gmail.com>
2026-04-27 01:59:16 +00:00

31 lines
1.7 KiB
SQL

-- Rename player fields in matches table
-- First, add new columns as nullable
ALTER TABLE "matches" ADD COLUMN "player1P1Id" INTEGER;
ALTER TABLE "matches" ADD COLUMN "player1P2Id" INTEGER;
ALTER TABLE "matches" ADD COLUMN "player2P1Id" INTEGER;
ALTER TABLE "matches" ADD COLUMN "player2P2Id" INTEGER;
-- Copy data from old columns to new columns
UPDATE "matches" SET "player1P1Id" = "team1P1Id";
UPDATE "matches" SET "player1P2Id" = "team1P2Id";
UPDATE "matches" SET "player2P1Id" = "team2P1Id";
UPDATE "matches" SET "player2P2Id" = "team2P2Id";
-- Drop old foreign key constraints
ALTER TABLE "matches" DROP CONSTRAINT "matches_team1P1Id_fkey";
ALTER TABLE "matches" DROP CONSTRAINT "matches_team1P2Id_fkey";
ALTER TABLE "matches" DROP CONSTRAINT "matches_team2P1Id_fkey";
ALTER TABLE "matches" DROP CONSTRAINT "matches_team2P2Id_fkey";
-- Drop old columns
ALTER TABLE "matches" DROP COLUMN "team1P1Id";
ALTER TABLE "matches" DROP COLUMN "team1P2Id";
ALTER TABLE "matches" DROP COLUMN "team2P1Id";
ALTER TABLE "matches" DROP COLUMN "team2P2Id";
-- Add foreign key constraints for new columns
ALTER TABLE "matches" ADD CONSTRAINT "matches_player1P1Id_fkey" FOREIGN KEY ("player1P1Id") REFERENCES "players"("id") ON DELETE RESTRICT ON UPDATE CASCADE;
ALTER TABLE "matches" ADD CONSTRAINT "matches_player1P2Id_fkey" FOREIGN KEY ("player1P2Id") REFERENCES "players"("id") ON DELETE RESTRICT ON UPDATE CASCADE;
ALTER TABLE "matches" ADD CONSTRAINT "matches_player2P1Id_fkey" FOREIGN KEY ("player2P1Id") REFERENCES "players"("id") ON DELETE RESTRICT ON UPDATE CASCADE;
ALTER TABLE "matches" ADD CONSTRAINT "matches_player2P2Id_fkey" FOREIGN KEY ("player2P2Id") REFERENCES "players"("id") ON DELETE RESTRICT ON UPDATE CASCADE;