Ranter
Join devRant
Do all the things like
				++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
				Sign Up
			Pipeless API
 
				From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
				Learn More
			Comments
		- 
				
				Bogus names are much better for testing instead of real names/data. With real data you could leak someone's personal information. Or cause massive panic, like the case in Hawaii.
- 
				
				 retrix8027y@netikras oh, well I live under a large rock, so please do share the Hawaii incident 😁 I wouldn't ever use real names, but maybe not "Gary is a Dinosaur!" 😂 Maybe "This is a test only"? retrix8027y@netikras oh, well I live under a large rock, so please do share the Hawaii incident 😁 I wouldn't ever use real names, but maybe not "Gary is a Dinosaur!" 😂 Maybe "This is a test only"?
- 
				
				Once I accidentally sent out a document for client review where I had a marker that there was still some work to do, a big fat "BANANA" in yellow. Client was confused. ^^
- 
				
				 Ederbit7217yOnce I tested automated customer email responses and sent this to the client by mistake. Ederbit7217yOnce I tested automated customer email responses and sent this to the client by mistake.
 ---
 From: batman@xxx.com
 Does this product contain gluten?
 ---
 
 He was amused.
Related Rants








 Two unit tests, no integration tests.
Two unit tests, no integration tests.
 Oops!
Oops!
I just sent an automated email titled "Gary is a Dinosaur!" to a lot of humourless clients because the ancient application I was testing assumed I was in the production environment. 🙃
Lesson to self: stop using bogus names in testing.
Still, it could've been a lot worse... 😂
rant
environments
testing