feat: create deterministic fixtures for prisma seed - #142
Merged
3m1n3nc3 merged 2 commits intoAug 20, 2026
Conversation
7 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #126
Description:
This PR introduces deterministic, idempotent fixtures for the Prisma development seed dataset. It isolates mock user and module data into dedicated fixture files, assigns stable local-only IDs, and ensures that repeated seeding operations safely update existing records rather than duplicating them.
Changes:
prisma/fixtures/users.tscontaining local-only seed identities covering all expected test cases (verified learner, unverified learner, deactivated learner, admin, instructor, employer).prisma/fixtures/modules.tsisolating module data fixtures.prisma/seed.tsto rely on the new fixtures and implemented robustupsertoperations for users, modules, completions, credentials, and transactions.prisma/SETUP.mdwith instructions on seeding and explicitly resetting the dataset usingnpm run seed:reset.Acceptance Criteria Met:
SETUP.md.Verification Evidence (Two-run seed and fixture verification):
Run 1 Output:
Run 2 Output:
(Note: Totals remain exactly the same between runs, proving the idempotent nature of the seeding script.)