|
Sander Rossel wrote: Do you make test data fun?
..I have learned to first check what the test-data is being used for. If it can end up in a presentation to the customer or the boss, some jokes can be, ehrm.. unprofessional.
But yes, there's often a Bacon Ipsum in each multiline textfield. When creating test-data, I use a fantasized company that insures broom-sticks (complete with logo's ofcourse). The added bonus of reserving for Narnia or Mordor is that when an order actually accidentally makes it to production, it is (hopefully!) easily recognizeale as nonsense-data. So yes, next to humor it is also defendable as being usefull.
Sander Rossel wrote: I know some people, especially customers, need test data to be "the real thing".
How 'real' is data? And what data is involved? Do take into account that it may have some privacy-implications if you are going to use a copy of 'real data', like that it may need to be anonymized.
Remember, security starts with paranoia 
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
Eddy Vluggen wrote: The added bonus of reserving for Narnia or Mordor is that when an order actually accidentally makes it to production, it is (hopefully!) easily recognizeale as nonsense-data
Or a lawsuit for lots of spilled fuel! 
Eddy Vluggen wrote: How 'real' is data?
I used to work for meat processing companies (yes, as a vegetarian, I know...) so they had a product, like tenderloin, that I would use for testing. So whenever the customer tried to explain what he wanted and we looked at some test data together he would laugh at me for putting a tenderloin in an order by some French customer that never orders tenderloin and then having it shipped by some Russian transporter (while the customer was in France).
I really don't care what customer I ship too, or what transporter delivers the goods, none of that mattered for the test, but he just couldn't work like that.
So yeah, he'd recreate nearly every test case we had so it fit a real world scenario, whether it was important for the test or not.
|
|
|
|
|
Sander Rossel wrote: So whenever the customer tried to explain what he wanted
Hehe, made me think of this[^] site, but be warned, it can be a time-waster 
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
The best test data would probably include a large set of historical data. If your app doesn't cater for historical data, make it, and avoid all the guesswork on what to initially test with.
|
|
|
|
|
My test data is somewhat dry and flat, but my bugs are of the best quality... there are tears...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: but my bugs are of the best quality
Somehow I read "drugs" instead of "bugs"... 
|
|
|
|
|
Sander Rossel wrote: Kornfeld Eliyahu Peter wrote: but my bugs are of the best quality
Somehow I read "drugs" instead of "bugs"..
No you didn't, but Kornfeld just edited his post real quick.
And as far as quality goes, I can assure you the man stocks some pretty classy stuff. 
|
|
|
|
|
Not only test data. Years ago I worked for a company that archived documents. The documents were archived on CDs by robots, along with a viewer to view them when needed. I had to add two menu items, one to activate the toolbar and one to make it disappear.
Instead of naming them 'Toolbar ein' and 'Toolbar aus', I named them 'Einbartool' and 'Ausbartool', just for fun. Then we got the news that the UN wanted to use the archiving system and they quickly needed the viewer translated to French. They literally ripped it out of my hands as soon a I had written my last line of code and sent it to a translator. A day later we got a mail with the question:
"Qu'est ce que un 'Einbartool'?
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
That's awesome! 
I was particularly bad at French in high school, the language of Mordor... 
|
|
|
|
|
Depends on the project, some I do and some I don't. Typically, for the projects I pull from production to dev/test frequently I don't. But if I'm in the early phases of a project that hasn't seen the light of day yet, I'm more inclined to do so. Also, depends on my mood... and planetary alignment.
Jeremy Falcon
|
|
|
|
|
|
You know, the data that's on production (where developers test) 
|
|
|
|
|
Oh, the data submitted by the users...
|
|
|
|
|
We recently demonstrated a system to the manager of the primary user having put in test data where we labelled a module "Finance Management". This was a label on a view and we said straight away we could change it to anything he liked. Said manager spent the next 30 minutes explaining why the label was invalid.
He later wrote it up as a problem with the application.
Morale of the story, make you test data nonsense, not something close to reality, even a manager can't focus on nonsense for too long.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Mycroft Holmes wrote: even a manager can't focus on nonsense for too long.
OH! How I wish that were true!
Cheers,
Peter
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
Ouch, been there once
My guess is that those people are so extremely incompetent, and know it, that whenever they see something new, like "Finance Management", they freak out.
Giving you a thirty minute speech on why the label is invalid is just to verify his own knowledge and position.
Writing it down as a problem makes him feel powerful.
Mycroft Holmes wrote: even a manager can't focus on nonsense for too long
Why do you think that?
Managers made nonsense their job!
|
|
|
|
|
Managers have to be incompetent in order to be promoted out of harms way. I remember one, very senior manager asking me how to make a video player play. I suggested he should press the button with the word 'Play' on it. Blank response. He didn't even recognise sarcasm.
We're philosophical about power outages here. A.C. come, A.C. go.
|
|
|
|
|
Mostly not. But recently I found test data for an application I was working on to mention occupation as terrorist. Don't know who created that but we were scared to deny anything to that particular user.
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
Generally I use a copy of the real data to make the testing more faithful.
But if I don't have real data and create a mockup, it has to be obvious that the test data is fake so I don't forget to exchange it for real data later, so yes hilarious it is. Or bacon ipsum[^] if I'm lazy.
|
|
|
|
|
|
I've gotta use the pirate ipsum some day.
|
|
|
|
|
I think we can, and in fact should, however never take it too far indeed.
Same for commenting code.
If it does come in production, always remember, someone signed of for going live at some point. As long as that person is not you, don't sweat it 
|
|
|
|
|
It can be extremely noisome, particularly if you have to arrange presentations or training for customer representatives.
One "very funny gag" can cost hours of time, editing it out of screenshots, rebuilding databases, etc.
I would strongly suggest that it be avoided, if you want your customers (and other people in your company) to view you as a professional.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Or just never use a development database for demos.
A development database is going to have test data, probably even some invalid data to test certain scenarios.
|
|
|
|
|
It's only after the contract is fulfilled that you have a production database, so the vast majority of demos are done with development databases, to describe to/train customers on "what you are going to get", and the docs guys can't wait until the product is installed and working customer-side to produce umpty-bagillion pages of documentation for it.
One aspect of professionalism is that of not giving your colleagues a sh1tty time for no good reason.
Another is that of not wasting money -- the guys who have to spend hours, days, and weeks making corrections to cover the little jokes have to be paid for their time.
Another is that of not putting the company in the position of being embarrassed in front of customers.
Could you remind me again what the plus side of the little jokes is?
If you want to joke, come to the Lounge; don't go to potentially customer-facing material.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
