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.
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