--

Scott Barber

President & Chief Technologist, PerfTestPlus, Inc.

Vice President & Executive Director, Association for Software Testing

www.perftestplus.com

www.associationforsoftwaretesting.org

"If you can see it in your mind...

     you will find it in your life."

It's true - people who don't get TDD hear the word 'Test' and all but ignore the 'Driven Development' part of it... sometimes to the point that they assume "oh, that's that testers job then"... or the opposite happens when you hear "doesn't that mean developers spend time testing when they should be writing code?"... It can take long and hard to break through this initial cultural barrier... For a long time I've searched for a way other than dropping the word 'T' in 'TDD' to break through the inevitable barrier and I'd almost given up hope... to the point where I was about to resort to the BDD philosophy. The benefits of test-infection made me persist.

To try to get people to understand the 'Driven Development' aspect of writing customer tests first a.k.a. "Acceptance Test Driven Development" (ATDD) and the relevance of the test and testing and testers and let's not forget early and frequent customer feedback... I've been using a different approach. It doesn't solve all of the problems caused by the letter 'T' but it does solve one of them - the part where people ignore the fact that the tests are driving development (yes I said 'tests' not 'testers' - I emphasise this because someone recently asked me 'so, how exactly do the testers drive the developers?').

So... let's talk about something else for a second... I want you to stop thinking about testing... for one moment. I want you to forget about the word 'test' and all the connotations that go along with it... I want you to think about something else... something random... let's say... 'Internet Radio'...

The American Homeland Security megadepartment has been in the news recently, covering a whole taxonomy of bug types, relating to people seen as unwelcome visitors and unwelcome visitors seen as raindrops! Firstly, we have the sad story of honest Debbie Williams Arthur who tried to renew her Virginia driver’s license over the net, only to have it rejected with a message saying her car stickers had to be picked up in person. Her husband went to pick them up, only to be told it had to be Debbie, and she had to call a toll free number in the meantime. When she rang the number she was told that Homeland Security had identified her as a fugitive called Debbie K Williams from another part of the U.S, and to bring her ID in to the office. When she got there, they said the problem would be fixed in 15 minutes, then she was told after an hour there were complications. These included the fact that the system didn’t think she existed and the Homeland Security override would not allow her records to be set up. After 3 ½ hours she left, after being advised to walk home because any police check would result in her arrest as a fugitive! She ended up with a hand written note (!) for the police in case she was stopped. Despite being told the issue would be fixed and she’d be given phone updates, none came. Finally after another visit to the office, she got her car stickers (at which point she probably was a fugitive driving with expired car stickers!). This is a production bug, relating to data. The system as a whole works, but missing data and locks on the existing data from the external homeland security system presumably needed software fixes to rectify the bug.

Here’s a question that I didn’t realize I had much to say about until I read my own response.

 

The Question:

Software Development: Is it an art or a science? An age old question I know, but what do you think and why?

 

My Response:

 

I refer to new software development as a scientific art. I've seen some maintenance work, platform porting, etc. that has been almost entirely mechanical -- I'm not sure what that counts as, but I certainly didn't witness anything "artistic".