Earlier quoted context omitted.
I learned a long time ago to be very careful with mock, dummy, or test data.... because some people will just push anything to prod, take screenshots during your demo and paste it into the official documentation... you name it. I was giving a demo on how to set up multiple computers in a federated setup using Active Directory, ADFS, etc... I had about 5 VMs named things like Hank, Peggy, Bobby, Boomhauer, Bill, and a…
I've never really understood developers' apparent need to add cutesy stuff into their work product's test data, variable names, easter eggs and so on. Adding this stuff is all downside risk with no technical benefit that you can explain in a written postmortem that will be read by your boss's boss's boss. I mean, I get the motivation: You're working on a boring, dry, SeriousBusiness project, and have a creative itch…
Well, the problem is, in almost all the examples here so far, said stuff was not meant to go out into the public. If your customers end up seeing your product's test data and---heavens above!---variable names, there is an organizational issue that needs to be addressed, cutesy stuff or no cutesy stuff.
Also, isn't the point of QA testing just to throw all and any data to your system? Would you rather have a system that's tested against the eventuality that someone abuses UTF-8 in a textbox or a full SeriousBusiness system with zero whimsy and cutesy stuff? Someone's whimsy cutesy stuff is someone else's street address.
I think you just put a finger on why I absolutely loathe SeriousBusiness Banking Software: they were designed, implemented, and tested in a vacuum that even normal users end up putting a toe out of line that just breaks the assumptions of the spec. You have to be extremely average down to your name to peacefully coexist with them.