For test data I like to use different movie or comic book names for different epics.
So when we start a new epic with multiple user stories I decide this will be all star wars, or matrix or donald duck characters, etc etc. The nice thing about it is when certain test data gives unexpected errors in other parts of application its easy to track where the test data is from.
const binOfStoRajj = {};
Life Pro Tip - Jenny’s number also (usually) works at the grocery checkout line to get the advertised store member discount on items. Choose whichever area code you like, someone has likely set it up in the past.
Jim Bo Bob 555-867-5309 123 test Street, Testville Ca, 55555
Is my goto
From someone who does this for a living… vary your names and addresses. Less chance of collisions if your suite teardown fails to clean up properly. Depending on your needs, having a hard-coded unique name/address per test can be fine, or if you’re using Python, there’s a library called Faker that will generate ISO-valid test data. It’s also a bit easier to see where a teardown failed if maybe an exception got swallowed.
Also faker.js
I once made test users who were all named John Smith in different languages. I learned that basically every name is a variant of John.
Jan Smit (in Dutch)
const jennyFromTheBlockMy inner urge to oop that…
Should be 213 area code, not 123
