Systems & Software Talk 

Cure for ATDD

Does your automation test suite suffer from Automated Test Deficit Disorder (ATDD)? Are your automated tests often ridiculed because they:

• Cannot complete a task?
• Are object-focus challenged?
• Are self-destructive and do not produce meaningful results?
• Feel as if they cannot get sufficient host-CPU attention?
• Stare at windows for extended periods of time?
• Are ever-fearful of going straight to blue-screen hell?
• Feel as if they are in a constant gooey mess of learning phase?

You are not alone and there is hope.

Retryalia ^tm and Recoveratin ^tm in combination may be right for treating ATDD symptoms in your automation test suite, providing you adaptability and recoverability benefits. Retryalia ^tm in 187 of 200 computerinical trials proved effective at countering the effects of object-focus-loss and windows-fixation, thus reducing the rate of incomplete tasks. Retryalia ^tm should not be used in treating automated tests directed at applications using __VIEWSTATES, as network death is certain.

Recoveratin ^tm in 196 of 200 computerinical trials proved effective at countering null or useless automation test results for an application-under-test (AUT) borne of hasty and otherwise sloppy and inflated ego-driven application design and development practices. Specifically in these situations Recoveratin ^tm proved effective at countering both blue-screen hell fears and gooey mess. Speak to your management and recommend organization-wide training before using Recoveratin ^tm in your automation test suite. Recoveratin ^tm in your automation test suite will auto-file defect reports and reject applications not thoroughly development- tested and prematurely thrown over the wall. In these situations Recoveratin will profile AUT source code and via email automatically broadcast profiling results, and - recommend source code changes to your entire organization. Also in these situations Recoveratin ^tm has been known to locate and publicize source code on how-not-to project-manage, how-not-to-design and how-not-to-develop application websites.

Recoveratin ^tm computerinical trials showed no added benefit for automated tests in organizations which promote sound project management and application design and development practices.  

What are the causes of ATDD or Automated Test Deficit Disorder?

ATDD in most cases is a mere but costly misguided perception leading to the belief that the automated tests are at fault and incorrect. ATDD is usually triggered by poor organizational practices. Those poor practices drive misconceptions of automated testing. Of the many delusions suffered by management, one will find silver-bullet perceptions, notions that it-is-just-record-and-playback, and any-monkey-can-do-it mindsets. ATDD is also caused by unskilled automation-tool implementers. In situations where ATDD is the result of deceptive and unskilled automators, Recoveratin will simply lock out the test-automator and to the test-automator, recommend a new job matching the would-be automator’s skills-of-deception, such as bonus-administrator at AIG.

In those very common situations where management delusions are bountiful and the AUT is clearly one which commands very low-levels of organizational pride, another benefit of Recoveratin ^tm is triggered. In those situations Recoveratin ^tm is known to change perceptions and counter delusions. Recoveratin ^tm will automatically administer Boostaplatformalis ^tm.  Boostaplatformalis ^tm is intended to enable, optimize and showcase deserving robust automation test suites and redirect the undue blame-driven scrutiny to the root cause – the AUT and the processes and practices (or lack thereof) which produced the application. With a periodic injection of Boostaplatformalis ^tm your automation test suite will perform effortlessly and not be the subject of undeserving scrutiny.

How does Boostaplatformalis ^tm work? Boostaplatformalis ^tm gathers intelligence about your entire organization and its network topology. Boostaplatformalis ^tm will use this intelligence to adapt itself and optimize its execution speed and programmatical correctness such that the AUT deficiencies and issues are always obvious.

What are some ways in which Boostaplatformalis ^tm works? Boostaplatformalis ^tm with its network topology intelligence, will automatically provision and order maximum bandwidth for itself – charging back to R&D. Boostaplatformalis ^tm will also order upgrades to network appliances and automatically create appropriate emails, service requests and work orders along the way. Boostaplatformalis ^tm will also order new automation test suite hosts to replace non-Mac hosts, or upgrades to existing hosts in the interest of eliminating automation test platform host security and performance issues, again charging back to R&D. If the new Mac automation test hosts have to be backordered, Boostaplatformalis ^tm will order Mac logos to serve as a placebo for the existing automation test platform hosts until Mac backorders can be filled.

 Let your automation test suite stand tall, proud, and erect.

 Order your Boostaplatformalis ^tm today!

(Mac is a product of Apple, Inc.)

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…”

The Collapse of JakeBrake Investments, Inc.?

JakeBrake Investments, Inc. (JBII) has been in business for 12 years. JBII has a proven track record grooved with sound business management practices. JBII co-founders have a proven bi-partisan relationship.  Co-founders JakeBrake and Mrs. JakeBrake realized long ago that a successful business such as JBII requires honesty, integrity, properly aimed ideals, solid work ethic, and - is devoid of greed. At JBII you will not find the co-founders:

• Sitting on their Fannie and making bad investments at the expense of others.
• Sporting capitalistic-excess-success smirks and doing the Freddie in celebration.
• Engaged in Partisan pettyship modeled after conflicts most often found on elementary school grounds during recess.
• Catering to voices backed by vast amounts of money while they forget their true purpose and who they actually represent.
• Sitting on their Fannie, watching the Indy 500 while eating a Big Mac – getting fat on false “nutrition”.
• In an expensive corporate aircraft fueled by excess and lofty egos.
• Sitting on leather chairs behind cherry-wood, marble-inlaid conference tables with catered Perrier (the non-anti-freeze mix).
• Risking all by driving down a street and running into a frenzied Wall.

You will not find Co-founders JakeBrake and Mrs. JakeBrake:

• Allowing their General self-sufficiency Motors to go without proper maintenance.
• Engaging in pity-me expressions containing, Chry, Slur, or other forms of expression used to dodge accountability.

JBII Co-founders JakeBrake and Mrs. JakeBrake cannot Uh Ford such behaviors.

JakeBrake and Mrs. JakeBrake will always maintain their modest, non-flaunting-of-excessive-capitalistic-success, low-frontage-cost, non-sky-reaching, non-marbled, non-glass-walled, non-lobby-pianist-equipped, non-executive-parking-stall-equipped corporate headquarters in the USA,  and - do their American-citizen tax-paying duties – on time with the full-amount owed.

Times have certainly changed. You will now find JBII on the brink of collapse as JBII co-founders JakeBrake and Mrs. JakeBrake scramble to aid in the rescue of large corporations who cannot repeat the success of two non-MBA-equipped, non-law-degree-equipped individuals.

Mrs. and Mr. JakeBrake are certainly not dancing the Freddie, nor are they taking American tax-payer $$ to fund research intended to understand the differences between the poop of the red and the poop of the gray squirrel; with an option for additional funding to determine how the poop of an albino squirrel contributes to global warming.

BodyBinary - LoadRunner (tm) or Other Script

Have you ever looked at body binary in a performance test tool script and wished you:

1.       Had a mullet hairdo so you could pull every last hair out, or

2.       Saw someone nearby with a mullet so you could pull that hair out, or

3.       Had a 20 Megawatt megaphone with you at a K-Fed concert for some heckle-fun, or

4.       Had some designer “meds” on hand?

You are temporarily mystified, or if you are breathing from an inhaler; you are mistified. Clearly you want to see what is inside that gobbled gook to determine what might be needed for parameterization or correlation. Here is one method for a quick glimpse into body binary. See for yourself and do the following:

1.       Highlight and Copy the below

2.       Paste into Wordpad or Notepad

3.       Find/Replace \x00 with nothing. Do not input anything in the Replace with text box

4.       Observe

"BodyBinary=ADCClientVersion:01.06 Content-Type: multipart/mixed; boundary=ge-')”

“pk(al8_,?800-555-1212/,; num-args=4 --ge-')pk(al8_,?1212/, Content-Type:”

“application/x-varg Content-Length: NNN \x08\xMySRV \x08\x02T\x08\xFC\x02”

“\x00S\x00e\x00l\x00e\x00c\x00t\x00 \x00A\x00. \x00B\x00E\x00E\x00R\x00, \x00 \x00A\x00. \x00B\x00R\x00E\x00W\x00E\x00R\x00, \x00 "

"\x00A\x00. \x00B\x00E\x00E\x00R\x00_\x00V\x00E\x00N\x00D\x00O\x00R\x00, \x00 \x00A\x00. \x00P\x00C\x00T\x00G\x00_\x00A\x00L\x00C\x00O\x00H\x00O\x00L\x00 \x00”

“\x00f\x00r\x00o\x00m\x00 \x00F\x00A\x00V\x00O\x00R\x00I\x00T\x00E\x00_\x00B\x00E\x00E\x00R\x00S\x00, \x00 "

"\x00w\x00h\x00e\x00r\x00e\x00 \x00 (\x00A\x00. \x00P\x00C\x00T\x00G\x00_\x00A\x00L\x00C\x00O\x00H\x00O\x00L\x00 \x00>\x00 \x007\x006\x00. \x000\x00 \x00 “

“\x00O\x00R\x00D\x00E\x00R\x00 \x00B\x00Y\x00 \x00P\x00C\x00T\x00G\x00_\x00A\x00L\x00C\x00O\x00H\x00O\x00L\x00 ",

LAST);