CI / skip-ci-check (pull_request) Successful in 5s
CI / docker-ci (pull_request) Successful in 7s
CI / secret-scan (pull_request) Successful in 12s
CI / viewer-unit (pull_request) Successful in 1m29s
CI / e2e (pull_request) Successful in 4m8s
CI / admin-unit (pull_request) Successful in 4m24s
Closes three items from the outstanding e2e/CI gap list: - Timing budgets: timings.measure() only ever recorded durations for the (still-unwired) Pushgateway export — nothing failed CI when a step got slow. Add e2e/timing-budgets.ts (expectWithinBudget + shared BUDGET_MS buckets) and wire it into every measure() call site across the suite. Mail-wait steps are deliberately left unbudgeted (external mail-trap delivery latency, not a code performance signal). - actions/upload-artifact@v4 doesn't work against this Gitea/act runner's artifact backend — pin to v3 for the e2e failure-report upload. - Shared act_runner npm cache has corrupted platform-native tarballs before (@next/swc-linux-x64-musl) and reds viewer-unit/admin-unit/e2e with no product bug involved. All three npm ci steps now retry once after `npm cache clean --force` on first failure. Verified: full local suite green against DEV (37 passed, 6 skipped, no budget assertion failures) before wiring into CI.
16 lines
559 B
TypeScript
16 lines
559 B
TypeScript
import { z } from 'zod';
|
|
import { test, expect } from '../fixtures';
|
|
import { BUDGET_MS, expectWithinBudget } from '../timing-budgets';
|
|
|
|
const HealthSchema = z.object({ status: z.literal('ok') });
|
|
|
|
test.describe('api @smoke', () => {
|
|
test('backend /health returns ok', async ({ api, timings }) => {
|
|
const res = await timings.measure('api_health', () =>
|
|
api.get('/health', { expectedStatus: 200, schema: HealthSchema }),
|
|
);
|
|
expectWithinBudget(timings, 'api_health', BUDGET_MS.api);
|
|
expect(res.data).toEqual({ status: 'ok' });
|
|
});
|
|
});
|