Systems & Software Talk 

Project "Success" Metrics & Project Development Methodology

Software Testing Misunderstandings and Disrespect

Software Testing & Quality Assurance

Part 1 – Software Testing Misunderstandings and Disrespect

This is Part 1 of a multi-part blog entry. Part 1 here is a setup for the nuts and bolts of remedies to be blogged in Part 2. If you wish to participate and have ideas as to how our profession can reverse the trend (assuming you agree there is a negative trend) described within, by all means comment here to Part 1 and I will include your ideas in Part 2.

Introduction

Is it time for a globally-based initiative to correct misunderstandings of what we do and restore respect to the software testing profession? Have too many organizations and individuals minimized the importance of what we do? Is overall respect waning for what we do and what we bring to the table? Do organizations still profile test engineers and classify them as lesser creatures relative to BAs and developers? I think so. My red flags began to unfurl in the wind of the apparent misunderstandings and diminished respect exposed in various posts as SQAForums as well as at the links below:

http://www.wisegeek.com/how-can-i-become-a-software-tester.htm

http://www.gamecareerguide.com/features/372/the_acid_test_qa_as_a_bridge_to_a_.php?page=1

Thanks to the people who located these and thanks to Anna Baik for her post at the below link which further exposes the public misunderstanding.

http://www.softwaretestingclub.com/forum/topics/would-you-recognise-your-job

Where Do We Fit Into This?

 Here are my thoughts.  I must insist however that you as a reader of this material are part owner in this dilemma and worldwide erosion of the public respect shown this profession. The amount of hidden misunderstandings and disrespect cannot be quantified of course and only you the “recipients” can speak to such. I suggest we are all partly responsible for restoration of software and systems testing to a more respectable position. Does that sound like a deal? I believe the core reasons for the continued and seemingly growing disrespect and misunderstandings of our profession are rooted in the following main reasons. I think the number one reason may surprise some and the other core reasons or symptoms are irrelevant if the main reason is addressed.

1.       We allow it to happen and do little to stop and correct this problem.

2.       Many organizations have structured departments and compensation based upon those very misunderstandings.

3.       Because of item 2, we now have an established culture based upon myths and misunderstandings – a culture that because of all the above wrongly but naturally promotes disrespect.

4.       Consulting firms are quick to put profit $$ before the customers’ best interests where they offer unqualified human resources for test engineering roles. This phenomenon is rampant in our industry and is very damaging to the credibility of our profession.

$$ Background

First I would like to summarize one big aspect of this pickle – something we are all aware of. Publicly traded companies rightfully intend to be profitable. The stockholders rightfully expect a return on their investments. Obviously employee/contractor compensation is one of many factors which can affect the profit margin. The global recession has caused some governments to bring a microscope to bear on compensation for certain corporate positions. In the context of this article, I am alluding to imbalance of compensation that may directly or indirectly affect all of us. I will leave my opinions aside with respect to that difficult issue and move on to another thought stream – that of globalization and outsourcing. First of all, I am in favor of globalization for (among many other reasons I will omit) the opportunity to learn about my sisters, brothers, their cultures and their languages.  I am rightfully skeptical of the total intent of outsourcing. (Note! My opinions and feelings are not those of, are independent of and do not necessarily align with or otherwise agree with those of my employers.) The intent of outsourcing is/was to cut costs and increase profitability. That is fair. It sure makes me as a stockholder smile. On the other hand, one might ask, “How much of outsourcing is exploitation?” I will leave that to you to ponder and get back to the issue of software and systems testing respect.

QA versus Software Testing

You may have noticed that other than the topic title I avoided the use of “Quality Assurance”. I did that for a reason. It is my belief that restoration of reasonable respect for software and systems testing begins with terminology – terminology which can effectively set expectations of our profession.  If the consumers of our skills and services have a good understanding of what to expect from us, they might better appreciate the value of what we bring to the table and treat us differently. It seems to me that having reasonable expectations of an employee or contractor is certainly a crucial success element, and is based in proper terminology which can yield proper expectations. On that note I offer the following terminology-related thoughts. Agreement with, or disagreement with what preceded and what follows is certainly your right. The point of this is not to change your beliefs. It is intended to offer up thoughts and possible avenues to restore a level of respect for our profession.

I believe that one can test and identify defects in systems and software until the cows come home. Assume that all defects identified are corrected after the cows arrive at home. Sure, when the defects existed they certainly lowered the level of quality. But there is absolutely no guarantee that a corrected and near-defect-free system or software application is of high quality. I think many of us have seen near-defect-free software of extremely poor quality. Therefore I submit to you that the purpose of software and systems testing is to identify defects, with a collateral responsibility to push for better software engineering processes/practices and quality awareness. It seems to me that it is then perfectly reasonable to suggest that the role of a Quality Assurance Engineer is to push for quality and do what it takes to reasonably prevent defects. However, “push for quality” and “prevent defects” is just not a sufficient guarantee that systems and software will be of high quality – correct? Typically, many of us are not in the position to stop the release of something we believe to be of poor quality. Therefore if we are not sufficiently empowered to stop poor quality from being released, why should we implicitly assume such empowerment by stating that we are a Quality Assurance person? Take another look at the last few sentences and questions. If the efforts of System/Software Test Engineers and Quality Assurance Engineers cannot guarantee quality, then who can? It seems to me that an organizational effort is required in order to give the terms “product” and “quality” a fleeting chance of earning the label “quality product”. Ask yourself before you disagree with me, "Can you in your role - alone, Assure Quality?" It seems to me that the bulk of the people who can assure any hope of quality are found at executive and management levels and in the early stages of a program or project where the seeds of quality will either be fertilized or ignored.

Many of us are aware of the famous “Quality Triangle”. I think it important to pay homage to that with respect to quality ownership and the key factors that play a huge role in determining a chance at product quality. Here is another variation on that famous artifact:

http://en.wikipedia.org/wiki/Project_triangle

Examples of Disrespect

I am sure we can all cite numerous instances of disrespect. As I alluded to previously there are countless instances of disrespect documented on the www.  One of my many many favorites is a classified ad from several years ago where the ad stated in part, “Quality Assurance Tester… with an opportunity to advance to software development.”  Let that and similar instances be our motivation to reverse this culture.

Granted it takes years to change a culture or climb this mountain. Bear in mind that the while the Earth’s tallest mountain is daunting to many, it is routinely conquered.

And in summary, perhaps I am just over-reacting to something I can do little about?? At age 60, should I even care?

End Part 1 - Setup

I really struggled to be serious throughout this entry. I wonder if Part 2 – Corrective Action will suggest that we all get mullet hairdos? “My achy breaky app…”

Happy Holidays 2007

I love the melodies of Christmas carols. I am an amateur MIDI enthusiast and have a goal of publishing a Christmas CD consisting of my own arrangements. I am inspired by the works of Mannheim Steamroller.

I have included two links here to free downloads of my work. Both songs are in WMA format and less than 5MB each.

• Hark
• Drummer

The first was put together on a Commodore Amiga 2000 accelerated with a 68020 card. I used Octamed to do the sequencing, driving a Rhodes (Roland) 660 keyboard. For the second song I used and for current work use Cakewalk and or FL-Studio aboard a 64-bit WIN-XP PC. I use these to drive the following:

1. Rhodes (Roland) 660 keyboard
2. Yamaha S03 Synthesizer keyboard
3. Roland SC-33 Sound Canvas, and
4. a Hercules Game Theater external sound card.

The Hercules card has the core Yamaha sound library. The Yamaha S03 goes far beyond that in terms of sounds.

Acceptance Testing (UAT) - Some Answers to Some Questions

Quality Assurance / Test Engineer Bill of Rights

Observe your timepiece. I am about to tell you what time it is with your own timepiece.

Be you a QA Analyst/ Engineer or Test Engineer/Analyst or Tester, your inherent rights as a Quality Assurance Professional are as follows. You have the right to:

1. Seek improvement in industry, organizational, departmental, or team-originated professional works, methods, methodologies, processes and practices.
2. If it does not fit, tactfully challenge, question, and debate any method, methodology, process, practice and any related material.
3. Be instinctively skeptical of any material put in front of you.
4. Verify and validate any material put in front of you.
5. Critique any material put in front of you.
6. Understand that one methodology does not solve all problems.
7. Exercise your most basic instinct – find the flaws.
8. Understand the meaning of the word theory.
9. Be the best you can be and tactfully influence others to do the same.

What other rights do you feel could be listed here? Could any of the above be improved?