We do it so it's obvious it's test data, and also we're lazy to think of more "real" data.
Just say some users expect real(ish) data for testing. I had a client who was totally not happy when he saw Batman and Superman in the test data.
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 test user HHill, 123 Rainy Street, Arlen, TX -- someone screenshotted and took notes during the demo and now that's in some formal training somewhere material. Thankfully, it's all internal.
When I and doing dev work and I need an available port, just any port, I use 666 -- because it's never used by anything and also DOOM. I gave a sprint demo and I used 660 instead of 666 to demo that the customer can specify the port number of screen X. Someone put that in the internal and also customer facing documentation... so now my company's product is default setup on 660, even thought it's completely user-configurable. Thank God I didn't demo with 666...
I mean, I get the motivation: You're working on a boring, dry, SeriousBusiness project, and have a creative itch that needs to be scratched. We all have a nonzero desire for a little joy and irreverence at work. But, man, scratch that itch with hobby projects, not stuff that's going out into the public! Or start a "wear a funny shirt day" at work or something like that. I know this is unpopular and makes me look like Debbie Downer, but our projects already have enough technical risks without deliberately adding more.
For a project that involved creating fake companies and user records, I purposely choose to use characters from Star Trek, Star Wars, and the Simpsons for each of the different companies. They're whimsical, non-offensive, and as an added bonus, if I see Homer Simpson listed alongside James T. Kirk, I instantly know there's a data integrity problem.
[0] Recent example: tissue sample, species: dog, tissue type: bone. Valid combination, just not present anywhere in prod.
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.
Variable names are different, and I'll give you that, but creating humorous dummy data in lower environments shouldn't ever be an issue. Injecting a little fun legitimately helps overcome despair, and the harder and more difficult your project/company is, the more it needs a dose of lightheartedness.
No matter what the scrum boards that reduce us to story points say, we're all human beings. When everything is very high stakes, you're in a perpetual state of fight or flight. It's literally physiologically bad for you. Blowing off steam helps.
As a test of our new Sev1 alerting system, I created a phony alert "The hordes of Mordor are descending upon our data center".
It was well received by the team.
I can't remember the details, but I've heard a story multiple times about a fake-sounding name being used in testing -- I think US military payroll? -- and causing problems when a real person had that name. Can anyone here remember this?
In any case, "batman" is just about plausible enough that it could be real. I tend to use names like "Mr. Testy Testalicious" which (a) contain the string "test", and (b) are so wildly absurd that I'm confident nobody will ever collide with it.
Tim: There’re so many places we could start, but in the process of doing homework for this, I found mentioned, and I wanted to do a fact check on this, of you having plane tickets automatically cancelled, and other issues related to your last name. Is that accurate? Did those things actually happen?
Caterina Fake: This has happened to me many times, in fact. And I discovered that it was actually the systems at KLM and Northwest that would throw my ticket out, my last name being “Fake.” And I have missed flights and have spent way too many hours with customer service trying to fix this problem. Here’s another thing too, is that I was unable for the first two years of Facebook to make an account there also. And probably all of my relatives.
https://www.bbc.com/future/article/20160325-the-names-that-b...
So, as a public service, I’m going to list assumptions your systems probably
make about names. All of these assumptions are wrong. Try to make less of
them next time you write a system which touches names.
> People’s names are all mapped in Unicode code points.
So... what? What do I do with this? My program has to use something to represent text, and since I fail to be a large multinational consortium, I can't invent my own character set and expect it to work.
Also:
> Confound your cultural relativism! People in my society, at least, agree on one commonly accepted standard for names.
This is pretty much true in countries with naming laws, yes.
> People have names.
People in a database will have certain records which will not be NULL. Whether you call one of those records a 'name' outside the context of that database really isn't my concern.
Try to understand these issues or rather how they could affect your business processes and software implementations down the line rather than dismissing them on a technical level.
You can store the Unicode representation just as you normally would. But what you don't do is assume that your Unicode representation is the only representation of the actual name.
More concretely, there are names that have multiple equally valid ways of writing them. You can probably expect that usually the same one is used, but you should absolutely not require this when building your business processes.
Even more concretely, as an example there are transliteration or simplification / shortening rules that allow people with otherwise strange or long names to buy an airline ticket. The actual, real name may not be any of the ones you have in your system. This matters e.g. when searching for someone or in customer support.
As for people without names (or unknown names), you should probably recognize that the handling might differ by country. E.g. records with "John Doe" in the US might have to be handled differently: analogous to "NULL != NULL" in SQL John Doe != John Doe. Or maybe even "Jane Doe == John Doe" in some cases. See also "Fnu Lu" (First Name Unknown, Last Name Unknown) used in the US.
And although I don't have knowledge about all the countries in the world, it may very well be that this leads to situations where the "no name" has to be handled specially or at least understood to be a special case, completely differently from other cases.
It lists a few people, like "Daniel Batman (20 March 1981 – 26 June 2012) was an Australian sprinter." https://en.wikipedia.org/wiki/Daniel_Batman
A few DDG searches finds others with the surname Batman who are not famous enough to be on Wikipedia.
He was a kind of founding father. He negotiated a fake treaty to steal the land from the local Kulin nation. He wanted to call it Batmania.
Also responsible for organising hunting parties for bushrangers and multiple massacres and genocide of aboriginal people in NSW, VIC, and TAS.
Total fucking cunt.
Sorry, Richard. I hope you were more amused than annoyed.
Now all I can think of is, "of course, you'll be playing the part of Sans Testicles."
[0] https://www.vanityfair.com/hollywood/adele-dazeem-idina-menz...
Ralf Kramden 1060 W. Addision Chicago IL 60613 United States
I’d not considered that they might be the only client where everyone was fluent in Latin.
The Carthusians didn't use computers, and the Jesuits didn't need his help.
He is, himself, a weird character.
Every other environment had standard boiler plate corporate logo + whatever product name. We kept the meme stuff in Dev just so you could be visually reminded, "Oh right, this is the crazy broken one."
Queue 7 years later, an emergency where we just had to impress a new client with a demo of how the product would work. And of course, the only thing that was really in a semi-ready state...was Dev. We couldn't move it over to a different one for some stupid reason or another.
Number one comment after the demo? "This looks very unprofessional. We do not want a dog logo on the login page. Is your team taking this seriously?"
Sales & Marketing got wind of how consistent the data was in it and wanted a copy they could use in presentations and for trade-show exhibits. We all said absolutely not. But they went around us and got a copy anyway.
It did not go well when a potential customer made a comment about the name during a demo.
Lesson learned. Always use the word "Test" in your test data. Always.