-
-
Notifications
You must be signed in to change notification settings - Fork 300
397 lines (342 loc) · 12.4 KB
/
Copy pathci-tests.yml
File metadata and controls
397 lines (342 loc) · 12.4 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
name: CI Tests
on:
pull_request:
branches: [main]
paths:
- "SparkyFitnessFrontend/**"
- "SparkyFitnessMobile/**"
- "SparkyFitnessServer/**"
- "SparkyFitnessGarmin/**"
- ".github/workflows/ci-tests.yml"
push:
branches: [main]
paths:
- "SparkyFitnessFrontend/**"
- "SparkyFitnessMobile/**"
- "SparkyFitnessServer/**"
- "SparkyFitnessGarmin/**"
- ".github/workflows/ci-tests.yml"
jobs:
# Detect which components changed
changes:
name: Detect Changes
runs-on: ubuntu-latest
outputs:
frontend: ${{ steps.filter.outputs.frontend }}
mobile: ${{ steps.filter.outputs.mobile }}
server: ${{ steps.filter.outputs.server }}
garmin: ${{ steps.filter.outputs.garmin }}
migrations: ${{ steps.filter.outputs.migrations }}
steps:
- name: Checkout code
uses: actions/checkout@v4
- name: Check for changes
uses: dorny/paths-filter@v2
id: filter
with:
filters: |
frontend:
- 'SparkyFitnessFrontend/**'
mobile:
- 'SparkyFitnessMobile/**'
server:
- 'SparkyFitnessServer/**'
garmin:
- 'SparkyFitnessGarmin/**'
# Files whose change can break a fresh-install migration run.
# Includes the jobs' own execution path (workflow + script) so a
# change there can't break migration CI while the jobs gate out.
migrations:
- 'SparkyFitnessServer/db/migrations/**'
- 'SparkyFitnessServer/db/rls_policies.sql'
- 'SparkyFitnessServer/db/grantPermissions.ts'
- 'SparkyFitnessServer/utils/dbMigrations.ts'
- 'SparkyFitnessServer/utils/applyRlsPolicies.ts'
- 'SparkyFitnessServer/tests/migrate.script.ts'
- 'SparkyFitnessServer/tests/rlsPermissionMatrix.integration.test.ts'
- 'SparkyFitnessServer/package.json'
- '.github/workflows/ci-tests.yml'
frontend-tests:
name: Frontend Tests
runs-on: ubuntu-latest
needs: changes
if: needs.changes.outputs.frontend == 'true'
steps:
- name: Checkout code
uses: actions/checkout@v4
- name: Install pnpm
uses: pnpm/action-setup@v4
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: "24"
cache: "pnpm"
cache-dependency-path: pnpm-lock.yaml
- name: Install global dependencies
run: pnpm install --frozen-lockfile
- name: Run validation (Type Check, Lint, Format)
working-directory: SparkyFitnessFrontend
run: pnpm run validate
- name: Run tests with coverage
working-directory: SparkyFitnessFrontend
run: pnpm run test:ci
env:
NODE_ENV: test
- name: Upload coverage report
uses: actions/upload-artifact@v4
if: always()
with:
name: frontend-coverage
path: SparkyFitnessFrontend/coverage/
retention-days: 7
mobile-tests:
name: Mobile Tests
runs-on: ubuntu-latest
needs: changes
if: needs.changes.outputs.mobile == 'true'
defaults:
run:
working-directory: SparkyFitnessMobile
steps:
- name: Checkout code
uses: actions/checkout@v4
- name: Install pnpm
uses: pnpm/action-setup@v4
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: "20"
cache: "pnpm"
cache-dependency-path: pnpm-lock.yaml
- name: Install dependencies
run: pnpm install --frozen-lockfile
- name: Run validation (Type Check, Lint)
run: pnpm run validate
- name: Run tests with coverage
run: pnpm run test:ci
env:
NODE_ENV: test
- name: Upload coverage report
uses: actions/upload-artifact@v4
if: always()
with:
name: mobile-coverage
path: SparkyFitnessMobile/coverage/
retention-days: 7
server-tests:
name: Server Tests
runs-on: ubuntu-latest
needs: changes
defaults:
run:
working-directory: SparkyFitnessServer
steps:
- name: Checkout code
uses: actions/checkout@v4
- name: Install pnpm
uses: pnpm/action-setup@v4
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: "24"
cache: "pnpm"
cache-dependency-path: pnpm-lock.yaml
- name: Install dependencies
run: pnpm install --frozen-lockfile
- name: Run validation (Type Check, Lint, Format)
run: pnpm run validate
- name: Run tests with coverage
run: pnpm run test:ci
env:
NODE_ENV: test
# SPARKY_FITNESS_API_ENCRYPTION_KEY and BETTER_AUTH_SECRET are left
# unset here on purpose: vitest.config.ts generates per-run random
# fallbacks so no secret literal lives in the repo (secret scanners
# like GitGuardian flag hardcoded keys on every push).
# This job has no database. The RLS matrix runs by default, so skip it
# here; it is exercised in the migration-check job (which provisions
# Postgres). Without this it would fail trying to connect.
SKIP_RLS_MATRIX: "1"
- name: Upload coverage report
uses: actions/upload-artifact@v4
if: always()
with:
name: server-coverage
path: SparkyFitnessServer/coverage/
retention-days: 7
migration-check:
name: Fresh-install Migrations
runs-on: ubuntu-latest
needs: changes
if: needs.changes.outputs.migrations == 'true'
defaults:
run:
working-directory: SparkyFitnessServer
services:
postgres:
image: postgres:18.3-alpine
env:
POSTGRES_USER: postgres
POSTGRES_PASSWORD: postgres
POSTGRES_DB: sparky_test
ports:
- 5432:5432
options: >-
--health-cmd pg_isready
--health-interval 5s
--health-timeout 5s
--health-retries 10
steps:
- name: Checkout code
uses: actions/checkout@v4
- name: Install pnpm
uses: pnpm/action-setup@v4
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: "24"
cache: "pnpm"
cache-dependency-path: pnpm-lock.yaml
- name: Install dependencies
run: pnpm install --frozen-lockfile
# First run applies every migration against empty DB
# Second run reapplies the always reapplied rls policies, simulating restart
- name: Apply migrations on an empty database (twice = restart simulation)
run: pnpm run test:migrations && pnpm run test:migrations
env:
SPARKY_FITNESS_DB_HOST: localhost
SPARKY_FITNESS_DB_PORT: "5432"
SPARKY_FITNESS_DB_NAME: sparky_test
SPARKY_FITNESS_DB_USER: postgres
SPARKY_FITNESS_DB_PASSWORD: postgres
SPARKY_FITNESS_APP_DB_USER: sparky_app
SPARKY_FITNESS_APP_DB_PASSWORD: sparky_app_pw
# The schema + RLS policies are now applied and the non-superuser app role
# exists, so the permission matrix can verify every table's real RLS
# behaviour as the app role (superuser DB user seeds, app role is enforced).
- name: Verify RLS permission matrix
run: pnpm exec vitest run tests/rlsPermissionMatrix.integration.test.ts
env:
# Default-on (SKIP_RLS_MATRIX unset) — runs against the Postgres this
# job provisions, with policies already applied by the steps above.
SPARKY_FITNESS_DB_HOST: localhost
SPARKY_FITNESS_DB_PORT: "5432"
SPARKY_FITNESS_DB_NAME: sparky_test
SPARKY_FITNESS_DB_USER: postgres
SPARKY_FITNESS_DB_PASSWORD: postgres
SPARKY_FITNESS_APP_DB_USER: sparky_app
SPARKY_FITNESS_APP_DB_PASSWORD: sparky_app_pw
# Prove an existing deployment can upgrade cleanly: apply the base branch's
# migrations to an empty database, then apply this PR's new migrations on top.
# Catches migrations that only break against an already-populated schema (the
# inverse of the fresh-install check above).
migration-upgrade-check:
name: Upgrade-path Migrations
runs-on: ubuntu-latest
needs: changes
if: needs.changes.outputs.migrations == 'true'
defaults:
run:
working-directory: SparkyFitnessServer
services:
postgres:
image: postgres:18.3-alpine
env:
POSTGRES_USER: postgres
POSTGRES_PASSWORD: postgres
POSTGRES_DB: sparky_test
ports:
- 5432:5432
options: >-
--health-cmd pg_isready
--health-interval 5s
--health-timeout 5s
--health-retries 10
steps:
- name: Checkout code
uses: actions/checkout@v4
with:
# Full history so the base commit is reachable for the swap below.
fetch-depth: 0
- name: Install pnpm
uses: pnpm/action-setup@v4
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: "24"
cache: "pnpm"
cache-dependency-path: pnpm-lock.yaml
- name: Install dependencies
run: pnpm install --frozen-lockfile
# Apply base migrations, then this PR's migrations on top of the same DB.
# The schema_migrations table persists between runs, so phase 2 applies
# only the newly added migrations — exactly what an upgrade does.
- name: Apply base migrations, then this PR's migrations on top
env:
BASE_SHA: ${{ github.event.pull_request.base.sha || github.event.before }}
SPARKY_FITNESS_DB_HOST: localhost
SPARKY_FITNESS_DB_PORT: "5432"
SPARKY_FITNESS_DB_NAME: sparky_test
SPARKY_FITNESS_DB_USER: postgres
SPARKY_FITNESS_DB_PASSWORD: postgres
SPARKY_FITNESS_APP_DB_USER: sparky_app
SPARKY_FITNESS_APP_DB_PASSWORD: sparky_app_pw
run: |
set -euo pipefail
if [ -z "${BASE_SHA:-}" ] || ! git cat-file -e "${BASE_SHA}^{commit}" 2>/dev/null; then
echo "::notice::No valid base commit (BASE_SHA='${BASE_SHA:-}'); skipping upgrade-path check."
exit 0
fi
echo "Base commit: ${BASE_SHA}"
# Phase 1: apply the base branch's migrations to the empty database.
# rm -rf first so migrations added only by this PR are absent at base.
# Only the SQL (db/migrations + rls_policies.sql) is swapped to base;
# the runner itself (dbMigrations.ts/grantPermissions.ts/applyRlsPolicies.ts
# + test:migrations) stays at HEAD. So this validates HEAD's runner
# applying the PR's new migrations onto a base-SQL schema, not a faithful
# base-deployment rebuild. Runner regressions are caught by the
# fresh-install job above; this job targets schema-dependent migrations.
rm -rf db/migrations db/rls_policies.sql
git checkout "${BASE_SHA}" -- db/migrations db/rls_policies.sql
pnpm run test:migrations
# Phase 2: restore this PR's migrations and apply the new ones on top.
rm -rf db/migrations db/rls_policies.sql
git checkout HEAD -- db/migrations db/rls_policies.sql
pnpm run test:migrations
garmin-tests:
name: Garmin Tests
runs-on: ubuntu-latest
needs: changes
if: needs.changes.outputs.garmin == 'true'
defaults:
run:
working-directory: SparkyFitnessGarmin
steps:
- name: Checkout code
uses: actions/checkout@v4
- name: Setup Python
uses: actions/setup-python@v5
with:
python-version: "3.12"
cache: "pip"
- name: Install dependencies
run: |
if [ -f requirements.txt ]; then
pip install -r requirements.txt
fi
pip install pytest pytest-cov
- name: Run tests with coverage
continue-on-error: true
run: |
if [ -d tests ] || [ -f test_*.py ]; then
pytest --cov=. --cov-report=xml --cov-report=html
else
echo "No tests found, skipping..."
fi
- name: Upload coverage report
uses: actions/upload-artifact@v4
if: always()
with:
name: garmin-coverage
path: SparkyFitnessGarmin/htmlcov/
retention-days: 7