Articles

Please enter an article title, author, or keyword
Q&A about QA

"What do you do for a living?"
"I'm in QA."
"Oh. What's QA?"

Bernie Berger
Change Management Processes for Software Development versus Content Development

This article explores the differences between software and content development and suggests tools that can aid development, through the automation of processes.

TechWell Contributor's picture TechWell Contributor
White Paper: AutoDrive Technology

As a former developer, I have designed a technology that virtually eliminates the complications and ever-present record-playback methodology from the software industry. Instead, I have derived a 100% dynamic, data-driven automated scripting technology that utilizes completely ambiguous data entry techniques. AutoDrive Technology can and will run unattended using dynamic error handling functionality, thus providing the value Automated Testing tools were intended to provide.

Anthony A. Lombardo
e-Talk Radio: Paulk, Mark, 28 November 2000

Ms. Dekkers and Mr. Paulk discuss the history of standardized, high maturity processes in the field of software development.

Carol Dekkers
e-Talk Radio: Rothman, Johanna - Test Management 101

In this "Test Management 101" discussion, Carol Dekkers and Johanna Rothman talk about the role of the test manager; techniques for assessing the quality of the testing process; tips for new test managers; and "good enough" quality.

Johanna Rothman's picture Johanna Rothman
e-Talk Radio: Pettichord, Bret, 8 February 2001

Ms. Dekkers and Mr. Pettichord talk about why testers and developers think differently, and why they should think differently.

Bret Pettichord's picture Bret Pettichord
Exploratory Testing and the Planning Myth

There is a notion that exploratory testing is devoid of and incompatible with planning. Supporters and skeptics alike tend to have concerns that exploratory testing might not work in their organizations because of this perceived lack of planning. Is exploratory testing necessarily unplanned? Let's take a look at the nature of plans and how exploratory practices fit into the big picture.

James Bach's picture James Bach
Making Sure You Buy the Right Packaged-Software Solution

The slick brochure promises every feature you can imagine, and the sales rep assures you that his package will do just what your users want. But that's what the other vendor's sales rep said, too. Sound familiar? Karl Wiegers recommends several requirements development practices that can help you select the right commercial package solution. Key practices include identifying user classes, defining their use cases, creating test cases from the high-priority use cases, documenting pertinent business rules, and exploring the users' performance goals and other quality attributes.

Karl E. Wiegers
Snaring Black Widows in Ladybug Clothing

The mood in the meeting was grim. All eyes were trained on Doris, the head of customer support. Doris surveyed the room as she spoke..."We have a problem in the field with the new release. Sixty-three users reported unrecoverable errors this week—a record high. An additional 152 people reported crashes, but the software recovered after reboot. This morning, I talked to an irate user who said he'd uninstalled our software after it crashed on him five times in a row. He wanted us to give him a full refund plus expenses. In short, the users are really angry. What do I tell them? When will we have a fix?"

Elisabeth Hendrickson's picture Elisabeth Hendrickson
Hey Vendors, Give Us Real Scripting Languages

Most test tools come bundled with vendor-specific scripting languages that I call vendorscripts. They are hard to learn, weakly implemented, and most important, they discourage collaboration between testers and developers. Testers deserve full-featured, standardized languages for their test development. Here's why.

Bret Pettichord's picture Bret Pettichord

Pages

Upcoming Events

Jun 07
Oct 03
Nov 14
Apr 24