PairWave
Demo · read-only · no sign-inAJ
← Back to dashboard

Cleaning up test fixtures without nuking CI

andy/auth-svc-2·Acme Engineering/ auth-svcNot connected
andy/auth-svc-2·demo · autoplaying
cycle 0
◊
Let me map what's actually shared before proposing a factory — I'll grep the fixtures for duplicated seed objects so we consolidate the real overlap, not just things with the same name.
Greptests/**/fixtures/*.ts 'createUser|seedOrg'allowed
◊
Six near-identical createUser helpers across four suites, differing only in the org plan. One factory with overrides covers all of them. Want me to add tests/factories/user.ts and migrate the smallest suite as a proof?
AJ
@andy
Yes — migrate the billing suite first. Don't touch the others yet.
Writetests/factories/user.ts (+38)allowed
ACOperator chat
@andy keep the old helper as a re-export for one release so the other suites don't break mid-migration.
AJ
@andy
Good call — re-export the old name from the factory so nothing else has to change yet.
◊
Done. createUser now re-exports from the factory; billing suite is green (18/18). Every other suite is untouched and still passing.
⊙ permission requestedBash
rm -rf tests/billing/fixtures # stale, now unused
AJ
@andy
Our test fixtures are a mess — every suite ships its own copy of the user/org seed. I want one factory without breaking CI. Where do I start?
demo · read-only

Composer is disabled in the demo. In the real app, this is where you'd type a prompt — `@@bob/billing` to route, plain text to queue. Sign in to use it.

Sign in →