22 lines
1014 B
Markdown
22 lines
1014 B
Markdown
# Verify Postgres Bump & System Health
|
|
|
|
I will verify the system works after the Postgres version bump by resetting the environment and running the integration test suite.
|
|
|
|
## Execution Steps
|
|
1. **Reset Docker Environment**:
|
|
- `docker-compose down -v` to remove existing containers and incompatible volumes.
|
|
- `docker-compose up -d` to start fresh with Postgres 17.
|
|
- Wait for services to initialize.
|
|
|
|
2. **Initialize Database**:
|
|
- Apply all migrations from `migrations/*.sql` to `madbase_db`.
|
|
- Apply test schema from `tests/integration/setup_db.sql` to `madbase_db`.
|
|
- This will be done by piping the SQL files into `docker exec -i madbase_db psql -U postgres -d postgres`.
|
|
|
|
3. **Run Integration Tests**:
|
|
- Execute `npm test` inside `tests/integration`.
|
|
- This will run the Vitest suite covering Auth, Storage, Realtime, Functions, and Data API.
|
|
|
|
## Expected Outcome
|
|
- All tests should pass if the Postgres 17 upgrade is compatible and the system is healthy.
|