1 Star2 Stars3 Stars4 Stars5 Stars
Loading ... Loading ...

By James Bach
The short answer is: you never know for sure that a test has ended.
Case in point. The license plate on my car is “tester.” It looks like this:

On December 20th, I received this notice in the mail:

As you see, it seems that the city of Everett, which is located between Orcas Island (where I live) and Seattle (where I occasionally visit) felt that I owed them for a parking violation. This is strange because I have never before parked in Everett, much less received a ticket there. A second reason this is strange is that the case number, apparently, is “111111111″.
At first I thought this was a hoax, but the phone number and address is real. The envelope was sent from Livonia, Michigan, and that turns out to be where Alliance One Receivables Management, Inc. is based. They collect money on behalf of many local governments, so that makes sense. It all looked legitimate, except that I’m not guilty, and the case number is weird.
Then it occurred to me that this may have been a TEST! Imagine a tester checking out the system. He might type “tester” for a license plate, not realizing (or not caring) that someone in Washington actually has that plate. He keys in a fake case number of “111111111″ because that’s easy to type, and then he forgets to remove that test data from the database.
Praise the Humans
I called the county clerk’s office to ask about this. At first I was worried, because they used an automated phone service. But I quickly got through to a competent human female. What can humans do? Troubleshoot. She told me that there indeed was a record in their system that I owed them money, but that the case number did not refer to a real case. In fact, she said that the number was incorrectly formatted: all their case number start with a “10.”
“This can’t be right,” she said.
“Could it be test data? Are you just starting to use Alliance One?” I asked.
“We’ve been using Alliance One for years. Oh, but we’re just starting to use their electronic ticketing system.”
She told me I was probably right about it being a test, but that she would investigate and get back to me.
A few days later I received this notice:

So, there you have it. Someone ran a test on November 9th that did not conclude until December 23rd when it is stopped via a court order! Thank you, Judge Timothy B. Odell.
I’m sure this will appear on an episode of Law and Order: Clerical Intent one of these days.
Just imagine if this hadn’t been a parking ticket program, but rather something that told the FBI to go and break down my door…
Morals of the Story

Beware of testing on the production system.
Always give the humans a way to correct the automation when it goes out of control. (Hear that, Skynet?)
You never know when your test is over.
If your name is “tester” or “test” or “testing”, eventually you will show up as test data in somebody’s project. Beware also if your name is “12345″, “asdf”, “qwerty”, “foobar”, or “999999999999999999999999.”


Category: Buggy Products, Test Strategy, Testing vs. Checking

Você também pode querer ler

Comments are off for this post.