Development Data Seeds via Cypress #1938
Open
+232
−48
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.
Development Data Seeds via Cypress
What's New
This is an experimental nice-to-have for quickly populating a local db with an array of conversations, comments, participants, and votes.
Within the
e2e/
folder, simply runnpm run seed
or
CYPRESS_BASE_URL=http://localhost:5001 npm run seed
for a non-standard host urlfor some default seeding.
Optional parameters include
eg.
npm run seed -- --numVoters=10 --numConversations=3 --commentsPerConvo=5
Pros/Cons
Pros
This approach simulates a real user interacting with a headless browser (Electron by default).
Useful for testing the whole stack, and surfacing real bugs, performance issues, etc.
It's also conveniently piggy-backing on existing cypress custom commands and setup.
Cons
This is relatively slow and brittle, compared to seeding the db directly, or with API calls.
For large sequences (over 100 participants), I've had Electron crash after slowing down and running out of resources.