Don't Be Cute with Your Test Data - Revision history

Kevlin at 21:46, 17 August 2009

Kevlin — Mon, 17 Aug 2009 21:46:09 GMT

←Older revision		Revision as of 21:46, 17 August 2009
Line 19:		Line 19:
	* A programmer maintaining a legacy system has been told to add an error dialog, and decides to use the output of existing behind-the-scenes logging to power it. Users are suddenly faced with messages such as "Holy database commit failure, Batman!" when something breaks.		* A programmer maintaining a legacy system has been told to add an error dialog, and decides to use the output of existing behind-the-scenes logging to power it. Users are suddenly faced with messages such as "Holy database commit failure, Batman!" when something breaks.

-	* Someone mixes up the test and live administration interfaces, and does some "funny" data entry. Customers spot a $1m "Bill Gates-shaped ~~buttplug~~" on sale in your online store.	+	* Someone mixes up the test and live administration interfaces, and does some "funny" data entry. Customers spot a $1m "Bill Gates-shaped personal massager" on sale in your online store.

	To appropriate the old saying that "a lie can travel halfway around the world while the truth is putting on its shoes," in this day and age a screw-up can be Dugg, Twittered, and Flibflarbed before anyone in the developer's timezone is awake to do anything about it.		To appropriate the old saying that "a lie can travel halfway around the world while the truth is putting on its shoes," in this day and age a screw-up can be Dugg, Twittered, and Flibflarbed before anyone in the developer's timezone is awake to do anything about it.
Line 26:		Line 26:

	In summary, when writing any text in your code — whether comments, logging, dialogs, or test data — always ask yourself how it will look if it becomes public. It will save some red faces all round.		In summary, when writing any text in your code — whether comments, logging, dialogs, or test data — always ask yourself how it will look if it becomes public. It will save some red faces all round.
-
-
-
-	''Corollary: Don't make a user interface design "deliberately ugly, to make sure someone will change it". Inevitably, it will go live that way!''

Kevlin: Don't Be Cute With Your Test Data moved to Don't Be Cute with Your Test Data

Kevlin — Thu, 30 Jul 2009 14:53:38 GMT

Don't Be Cute With Your Test Data moved to Don't Be Cute with Your Test Data

←Older revision

Revision as of 14:53, 30 July 2009

Kevlin at 14:49, 30 July 2009

Kevlin — Thu, 30 Jul 2009 14:49:53 GMT

←Older revision		Revision as of 14:49, 30 July 2009
Line 1:		Line 1:
-	It was getting late. I was throwing in some placeholder data to test the page layout I'd been working on.	+	''It was getting late. I was throwing in some placeholder data to test the page layout I'd been working on.''

-	I appropriated the members of The Clash for the names of users. Company names? Song titles by the Sex Pistols would do. Now I needed some stock ticker symbols: just some four letter words in capital letters.	+	''I appropriated the members of The Clash for the names of users. Company names? Song titles by the Sex Pistols would do. Now I needed some stock ticker symbols: just some four letter words in capital letters.''

-	I used those four letter words.	+	''I used '''those''' four letter words.''

-	It seemed harmless. Just something to amuse myself, and maybe the other developers the next day before I wired up the real data source.	+	''It seemed harmless. Just something to amuse myself, and maybe the other developers the next day before I wired up the real data source.''

-	The following morning, a project manager took some screenshots for a presentation.	+	''The following morning, a project manager took some screenshots for a presentation.''

-	----

-	Programming history is littered with these kinds of war stories. Things that developers and designers did "that no-one else would see" which unexpectedly became visible.

-	The leak type can vary, but when it happens, it can be deadly to the person, team or company responsible. Examples include:	+	Programming history is littered with these kinds of war stories. Things that developers and designers did "that no one else would see" which unexpectedly became visible.
		+
		+	The leak type can vary but, when it happens, it can be deadly to the person, team, or company responsible. Examples include:

	* During a status meeting, a client clicks on an button which is as yet unimplemented. They are told: "Don't click that again, you moron."		* During a status meeting, a client clicks on an button which is as yet unimplemented. They are told: "Don't click that again, you moron."
Line 19:		Line 19:
	* A programmer maintaining a legacy system has been told to add an error dialog, and decides to use the output of existing behind-the-scenes logging to power it. Users are suddenly faced with messages such as "Holy database commit failure, Batman!" when something breaks.		* A programmer maintaining a legacy system has been told to add an error dialog, and decides to use the output of existing behind-the-scenes logging to power it. Users are suddenly faced with messages such as "Holy database commit failure, Batman!" when something breaks.

-	* Someone mixes up the test and live administration interfaces, and does some "funny" data entry. Customers spot a $1m "Bill Gates-shaped buttplug" on sale in your online store.	+	* Someone mixes up the test and live administration interfaces, and does some "funny" data entry. Customers spot a $1m "Bill Gates-shaped buttplug" on sale in your online store.

-	To appropriate the old saying that "A lie can travel halfway around the world while the truth is putting on its shoes", in this day and age a ~~screwup~~ can be Dugg, Twittered and Flibflarbed before anyone in the developer's timezone is awake to do anything about it.	+	To appropriate the old saying that "a lie can travel halfway around the world while the truth is putting on its shoes," in this day and age a screw-up can be Dugg, Twittered, and Flibflarbed before anyone in the developer's timezone is awake to do anything about it.

-	Even your source code isn't necessarily free of scrutiny. In 2004, when a tarball of the Windows 2000 source code made its way onto file sharing networks, some folks merrily grepped through it for profanity, insults and [http://www.kuro5hin.org/story/2004/2/15/71552/7795 other funny content]. (The comment "// TERRIBLE HORRIBLE NO GOOD VERY BAD HACK" has, I will admit, become appropriated by me from time to time since!)	+	Even your source code isn't necessarily free of scrutiny. In 2004, when a tarball of the Windows 2000 source code made its way onto file sharing networks, some folks merrily grepped through it for profanity, insults and [http://www.kuro5hin.org/story/2004/2/15/71552/7795 other funny content]. (The comment <code>// TERRIBLE HORRIBLE NO GOOD VERY BAD HACK</code> has, I will admit, become appropriated by me from time to time since!)

-	In summary, when writing any text in your code, whether comments, logging, dialogs or test data, always ask yourself how it will look if it becomes public. It will save some red faces all round.	+	In summary, when writing any text in your code — whether comments, logging, dialogs, or test data — always ask yourself how it will look if it becomes public. It will save some red faces all round.

-	----

-	Corollary: Don't make a user interface design "deliberately ugly, to make sure someone will change it". Inevitably, it will go live that way!

		+	''Corollary: Don't make a user interface design "deliberately ugly, to make sure someone will change it". Inevitably, it will go live that way!''

Rodbegbie: New page: It was getting late. I was throwing in some placeholder data to test the page layout I'd been working on. I appropriated the members of The Clash for the names of users. Company names? ...

Rodbegbie — Sun, 19 Apr 2009 22:50:38 GMT

New page: It was getting late. I was throwing in some placeholder data to test the page layout I'd been working on. I appropriated the members of The Clash for the names of users. Company names? ...

New page

It was getting late. I was throwing in some placeholder data to test the page layout I'd been working on.

I appropriated the members of The Clash for the names of users. Company names? Song titles by the Sex Pistols would do. Now I needed some stock ticker symbols: just some four letter words in capital letters.

I used *those* four letter words.

It seemed harmless. Just something to amuse myself, and maybe the other developers the next day before I wired up the real data source.

The following morning, a project manager took some screenshots for a presentation.

----

Programming history is littered with these kinds of war stories. Things that developers and designers did "that no-one else would see" which unexpectedly became visible.

The leak type can vary, but when it happens, it can be deadly to the person, team or company responsible. Examples include:

* During a status meeting, a client clicks on an button which is as yet unimplemented. They are told: "Don't click that again, you moron."

* A programmer maintaining a legacy system has been told to add an error dialog, and decides to use the output of existing behind-the-scenes logging to power it. Users are suddenly faced with messages such as "Holy database commit failure, Batman!" when something breaks.

* Someone mixes up the test and live administration interfaces, and does some "funny" data entry. Customers spot a $1m "Bill Gates-shaped buttplug" on sale in your online store.

To appropriate the old saying that "A lie can travel halfway around the world while the truth is putting on its shoes", in this day and age a screwup can be Dugg, Twittered and Flibflarbed before anyone in the developer's timezone is awake to do anything about it.

Even your source code isn't necessarily free of scrutiny. In 2004, when a tarball of the Windows 2000 source code made its way onto file sharing networks, some folks merrily grepped through it for profanity, insults and [http://www.kuro5hin.org/story/2004/2/15/71552/7795 other funny content]. (The comment "// TERRIBLE HORRIBLE NO GOOD VERY BAD HACK" has, I will admit, become appropriated by me from time to time since!)

In summary, when writing any text in your code, whether comments, logging, dialogs or test data, always ask yourself how it will look if it becomes public. It will save some red faces all round.

----

Corollary: Don't make a user interface design "deliberately ugly, to make sure someone will change it". Inevitably, it will go live that way!

By [[Rod Begbie]]

This work is licensed under a
[http://creativecommons.org/licenses/by/3.0/us/ Creative Commons Attribution 3]