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

“Combinatorial testing can detect hard-to-find software faults more efficiently than manual test case selection methods.” Developers of large data-intensive software often notice an interesting—though not surprising—phenomenon: When usage of an application jumps dramatically, components that have operated for months without trouble suddenly develop previously undetected errors. For example, newly added customers may have account records ...
Introduction Many companies have come to realize that software testing is much more than a task that happens at the end of a software development cycle. They have come to understand that software testing is a strategic imperative and a discipline that can have a substantial impact on the success of an organization that develops ...
Reducing the pester of duplications in bug reporting. Both software Developers and Testers need to be able to clearly identify any ‘Bug’, via the ‘Title’ used for the ‘Bug Report’.
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.
Has this ever happened to you: You’ve been testing for a while, perhaps building off of a branch, only to find out that, after all of this time, there is something big wrong. It’s a bad build and now you have to go backwards, fix something, and get a new build. Basically, you just wasted ...
When it is out of the question to delay delivery, the solution is a prioritization strategy in order to do the best possible job within the time constraints. The scenario is as follows: You are the test manager. You made a plan and a budget for testing. Your plans were, as far as you know, ...
LogiGear Magazine March Testing Essentials Issue 2017
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 ...
Jeff Offutt – Professor of Software Engineering in the Volgenau School of Information Technology at George Mason University – homepage – and editor-in-chief of Wiley’s journal of Software Testing, Verification and Reliability, LogiGear: How did you get into software testing? What do you find interesting about it? Professor Offutt: When I started college I didn’t ...
This is an adaptation of a presentation entitled Software Testing 3.0 given by Hung Nguyen, LogiGear CEO, President, and Founder. The presentation was given as the keynote at the Spring 2007 STPCON conference in San Mateo, California. Watch for an upcoming whitepaper based on this topic. Introduction This first article of this two article series ...
The 12 Do’s and Don’ts of Test Automation When I started my career as a Software Tester a decade ago, Test Automation was viewed with some skepticism.
Test organizations continue to undergo rapid transformation as demands grow for testing efficiencies. Functional test automation is often seen as a way to increase the overall efficiency of functional and system tests. How can a test organization stage itself for functional test automation before an investment in test automation has even been made? Further, how ...

Leave a Reply

Your email address will not be published.

Stay in the loop with the lastest
software testing news

Subscribe