---
id: w5/m2/t007
title: Test coverage
worker: worker5
status: done
estimate: 30m
depends_on: [w5/m2/t005]
---

## Objective

Add meaningful tests for the behavior this milestone shipped — primarily that Ory branding is actually suppressed (a real regression risk if config drifts back) — not a snapshot-everything or tautological suite.

## Context

- The most testable, non-visual assertion from this milestone is t002's `hide_ory_branding: true` config — a unit-level check that `dashboard/src/common/lib/ory/config.ts`'s `oryConfig.project.hide_ory_branding` is `true` guards against an accidental revert.
- Visual polish itself (spacing/typography) isn't meaningfully unit-testable — don't fake coverage with brittle class-name snapshot tests; rely on the manual review from t001–t005 for that part.

## Steps

1. Add a small test asserting `oryConfig.project.hide_ory_branding === true` (and any Component System override added in t002, if applicable — e.g. that the override function returns the expected suppressed component).
2. Run `yarn test` and confirm it passes.

## Files

- `dashboard/src/common/lib/ory/__tests__/config.test.ts` (new)

## Acceptance criteria

- [ ] A test exists that fails if `hide_ory_branding` is reverted to `false` or removed.
- [ ] `yarn test` passes with no snapshot-everything or tautological tests added.

## Out of scope

- Visual regression testing (out of scope for this stack; manual review only).
