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.

This can be generalized to say that programming has become such a diverse profession that you will find experts in one area that know very little about others. There’s simply too many things that are programmed in too many ways for anyone to know it all anymore. Hell, that was the case in the 70’s and 80’s too.

I’ve been using it to write unit tests, I still need to edit them to mock out some things and change a bit of logic here and there, but it saves me probably 50-75% of the time it used to take, just from not having to hand-write all that code.