Home > Software Quality Tips > Peak Performance > The controversy surrounding the schools of software testing
Software Quality Tips:
EMAIL THIS
 TIPS & NEWSLETTERS TOPICS 

PEAK PERFORMANCE

The controversy surrounding the schools of software testing


Scott Barber
12.08.2008
Rating: -3.50- (out of 5)


Software quality news and advice
Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google


Periodically, discussions break out in various software testing communities around the Web regarding the schools of software testing.

As I write this, there are discussions going in SQAForums, on the Software-Testing Yahoo! group, and various blogs that (at least up to the time I started writing this piece) reside on or are fed to Testing Reflections. In principle, I'm always pleased when these discussions break out. The point of identifying the schools in the first place was to increase the overall awareness of the diversity in ideologies, practices, and values (i.e. schools of thought) in our field and to stimulate discussion about the situational pros and cons of each. That said, the discussions that actually take place tend to drift off in one or more directions that end up being disappointing, unnecessarily confrontational, and generally not useful.

After witnessing this pattern, participating in these recent discussions, and listening to comments from those who followed the discussions for several years, I've identified several areas in which these discussions go awry. Below, I call those out and share my thoughts about each. But before I do, I would be remiss if I didn't remind folks of the following:

  • I am a self-identified member and champion of the Context-Driven School of software testing. Some people identify me as a thought-leader thereof.

  • I am, and have been for many years, a consultant, trainer and leader of various communities of software testers. As such, I encounter a lot of individuals and organizations who have their own unique collection of views, opinions, favorite practices, default processes, and personal preferences related to testing. For the most part, I've found these individuals and organizations to be thoughtful and effective as testers and to have valuable contributions to make to the field of software testing.

  • I believe that the fact that different people with different experiences in different organizations have different ideas about testing to be one of the best parts of our field.

  • I believe that standardizing on any one set of ideas about software testing would be among the worst possible things I could imagine for our field (even if they were my favorite ideas). Our diversity is our strength.

  • While I certainly have my own preferences and biases, I do not believe that they are best, or even appropriate, for every situation.

  • I like it when someone challenges my ideas. Especially when that someone is intelligent, thoughtful, experienced, educated, passionate, and in absolute disagreement with me about something we've both put a lot of thought into. Many of my best ideas are the result of debates I've had where someone shot holes in my theories, refuted my premise, or otherwise led to ...

    Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us    Add to Google



    RELATED CONTENT
    Peak Performance
    Ways to approach application performance testing on a tight budget
    Budget-friendly Web app performance testing, monitoring tips
    Testing rich Internet applications: 2009's best free tools
    Testing training: Disturbing behaviors of students
    Software testers are not helpless
    Software testers must understand the business side of software quality
    Software testing is improved by good bug reporting
    Why do we test for performance?
    Software testers: Identity crisis or delusions of grandeur?
    Magic formula for successful performance testing

    Software testing models and approaches (Context-driven, Factory, Analytic, Quality, IV&V)
    Software Testing: New software testing technologies bring new challenges
    Software Testing Ezines
    Recognizing appropriate scenarios for context testing
    Rich Internet applications security testing checklist
    Seven steps for a quality change and configuration management program
    How to create performance testing workload models
    How to apply modeling techniques to support software testing
    Transitioning from AJAX to .NET what changes to expect in RIA's
    Oracle VM Template Builder aims to speed deployment of VMs
    Why automated software testing fails and pitfalls to avoid

    RELATED GLOSSARY TERMS
    Terms from Whatis.com − the technology online dictionary
    black box  (SearchSoftwareQuality.com)
    context-driven testing  (SearchSoftwareQuality.com)
    load testing  (SearchSoftwareQuality.com)

    RELATED RESOURCES
    2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems
    Search Bitpipe.com for the latest white papers and business webcasts
    Whatis.com, the online computer dictionary


    me to enhance my own ideas.

Now that we've got all of that out of the way, my observations:

Some people seem to be offended by the notion of schools of software testing because they didn't like the tone or bias of a particular slide deck, article, presentation, or discussion about the schools.

Some people think because they don't fit neatly into a single school that it is their sworn duty to publicly oppose the notion of schools of testing.

Some people think that by naming and identifying schools of thought it encourages proponents of a school to act superior while vilifying the proponents of the others.

At the end of the day, if you want to debate whether the biases inherent to having testers fully integrated into the development team and reporting to the lead developer is more or less risky than the inevitable blind spots that result from completely isolating the test team from the development team when developing software for a regulated medical device, I'm all in. Interestingly, that one could find people to engage in such a debate demonstrates that there are differing schools of thought in software testing, and it suggests to me that naming and characterizing those schools of thought can only serve to help all testers and the organizations they serve make better decisions and recommendations about what ideas and practices are best for them -- at least for now.

----------------------------------------
About the author: Scott Barber is the chief technologist of PerfTestPlus, vice president of operations and executive director of the Association for Software Testing, and co-founder of the Workshop on Performance and Reliability.


Rate this Tip
To rate tips, you must be a member of SearchSoftwareQuality.com.
Register now to start rating these tips. Log in if you are already a member.




DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.



Software Design & Testing - Project Management
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
SEARCH 
TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.

TechTarget Corporate Web Site  |  Media Kits  |  Site Map




All Rights Reserved, Copyright 2006 - 2009, TechTarget | Read our Privacy Policy
  TechTarget - The IT Media ROI Experts