Rob Lambert: The Social Tester

Creative Director at the Software Testing Club, Rob Lambert always has something to say about testing. Lambert regularly blogs at TheSocialTester where he engages his readers with test cases, perspectives and trends.

“Because It’s Always Been Done This Way”

Study the following (badly drawn) image and see if there is anything obvious popping in to your head.

Now, you’ve probably got hundreds of questions going through your mind about testing, etc. But I want to draw your attention to the security and the value that this security is protecting. Let me backfill the story.

I went to a major electrical goods chain here in the UK. I wanted to buy a hard drive. I saw the one I wanted, behind the glass in the locked and secure glass cabinet. I asked the assistant if I could have one and it took her about 2 or 3 minutes to find the keys. It then took her about 2 minutes to open the cabinet, get the disk out and then lock it all back I then scanned just the two meter shelf next to the cabinet and it had about £3000 of Routers and Switches.

The glass cabinet had items that ranged between £30 and £89.49. Yet the shelf had items that ranged between £30 and £109.10.

It didn’t really make sense to me. If I were the store manager, I would be looking to secure the most expensive and valuable stock. Wouldn’t you? So I asked the lady why this was the case.

She said “Because it’s always been done that way. I guess I’d never thought to question it”.

I asked whether hard drives were the most stolen of items, fishing to see whether high targeted products were being secured over high value products. The lady didn’t know. I tried to find some stats but failed. I suspect it’s not got much to do with it.

The lady said that many displays, concepts and ideas came from head office and remained that way even if they were ineffective. It’s because it’s always been done like that… I guess.

And so I draw the comparison to testing, product design, feature sets and anything else we may ever get involved with in our daily work.

Why keep doing something when it is ineffective? Why spend months writing test documentation that no one reads? Why spend months writing test cases in minute detail to have to re-write them when you see the final product? Why always concentrate your security testing on the software when in reality the user is the biggest security gap? Why keep reporting that metric when no-one needs it?

Why not challenge the norm? The ineffective? The old rules and processes?

Why not suggest new and interesting ways of doing things? Why not improve or tweak processes for changing circumstances?

“Because it’s always been done that way”.

Do you have compelling reasons to leave something ineffective in place? Please let me know.

 

Email Rob Lambert at robk@thesocialtester.co.uk

 

Mark Levison

Creative Director at the Software Testing Club, Rob Lambert always has something to say about testing. Lambert regularly blogs at TheSocialTester where he engages his readers with test cases, perspectives and trends.
“Because It’s Always Been Done This Way”
Study the following (badly drawn) image and see if there is anything obvious popping in to your head.

Mark Levison
Mark Levison has over twenty years experience in the IT industry, working as a developer, manager, technical lead, architect, and consultant.

The Related Post

Internet-based per-use service models are turning things upside down in the software development industry, prompting rapid expansion in the development of some products and measurable reduction in others. (Gartner, August 2008) This global transition toward computing “in the Cloud” introduces a whole new level of challenge when it comes to software testing.
At VISTACON 2011, Jane sat down with LogiGear Sr. VP, Michael Hackett, to discuss complex systems.
People rely on software more every year, so it’s critical to test it. But one thing that gets overlooked (that should be tested regularly) are smoke detectors. As the relatively young field of software quality engineering matures with all its emerging trends and terminology, software engineers often overlook that the software they test has parallels ...
This article was adapted from a presentation titled “How to Turn Your Testing Team Into a High-Performance Organization” to be presented by Michael Hackett, LogiGear Vice President, Business Strategy and Operations, at the Software Test & Performance Conference 2006 at the Hyatt Regency Cambridge, Massachusetts (November 7 – 9, 2006). Introduction Testing is often looked ...
They’ve done it again. Gojko Adzic, David Evans and, in this book, Tom Roden, have written another ‘50 Quick Ideas’ book. And this one is equally as good as the previous book on user stories. If not even better.  
LogiGear Magazine – May 2011 – The Test Process Improvement Issue
Are you looking for the best books on software testing methods? Here are 4 books that should be on your reading list! The Way of the Web Tester: A Beginner’s Guide to Automating Tests By Jonathan Rasmusson Whether you’re a traditional software tester, a developer, or a team lead, this is the book for you! It ...
This article was originally featured in the May/June 2009 issue of Better Software magazine. Read the entire issue or become a subscriber. In my travels, I’ve worked with a number of companies that have attempted to assess the quality of their testing — or worse, their testers — using poorly considered metrics. Sometimes the measurement ...
David S. Janzen – Associate Professor of Computer Science Department California Polytechnic State University, San Luis Obispo – homepage LogiGear: How did you get into software testing and what do you find interesting about it? Professor Janzen: The thing I enjoy most about computing is creating something that helps people. Since my first real job ...
This article was developed from concepts in the book Global Software Test Automation: Discussion of Software Testing for Executives. Introduction Many look upon Software Testing as a cost. While it is true that Software Testing does cost money, in many cases significant amounts of money, it is also an activity that helps an organization to ...
With complex software systems, you can never test all of the functionality in all of the conditions that your customers will see. Start with this as a fact: You will never test enough! Step 2 in getting started is to read and re-read The Art of Software Testing by Glenford Myers. This classic will set the ...
The V-Model for Software Development specifies 4 kinds of testing: Unit Testing Integration Testing System Testing Acceptance Testing You can find more information here (Wikipedia): http://en.wikipedia.org/wiki/V-Model_%28software_development%29#Validation_Phases What I’m finding is that of those only the Unit Testing is clear to me. The other kinds maybe good phases in a project, but for test design it ...

Leave a Reply

Your email address will not be published. Required fields are marked *

Stay in the loop with the lastest
software testing news

Subscribe