Testing

Articles

Key Risks to System Quality

Before we can build a high-fidelity test system, we have to understand what quality means to our customers. Test professionals can avail themselves of three powerful techniques for analyzing risks to system quality. Targeting our testing investment by increasing effort for those areas most at risk results in the highest return on investment.

Rex Black's picture Rex Black
Telling Our Story

Software professionals learn a lot from technical presentations and articles. But sometimes a well-told story can illustrate technical concepts even better, in an entertaining and memorable way. This week, Lee Copeland tells why it's good to be a software bard, teaching your audiences hard concepts in a decidedly nontechnical way.

Lee Copeland's picture Lee Copeland
Institutionalizing Poor Quality

Have you ever noticed how many professional activities don't utilize a separate testing phase? Veteran tester and instructor Lee Copeland has. And it got him thinking about our industry and the role a tester plays. In this week's column, you may be surprised by his conclusions.

Lee Copeland's picture Lee Copeland
A Selection of "Our Take" Columns

"Our Take" is a regular column from the editors at Software Quality Engineering. It appears in the twice-monthly StickyLetter since its inception in September 2000 (originally "STQe-Letter"). From jazz music, to car troubles, to the Lewis and Clark expedition, Robert Rose-Coutré, former StickyMinds.com Editor, will use anything to make a point about building better software. The editors at Software Quality Engineering have compiled a collection of some of these pieces. Musings from StickyLetter's "Our Take" are presented here.

Robert Rose-Coutré's picture Robert Rose-Coutré
Bug Counts vs. Test Coverage

Occasionally, we encounter projects where bug counts simply aren't as high as we expect. Perhaps the product under test is in its second or third release cycle, or maybe the development team invested an inordinate amount of time in unit testing. Whatever the reason, low bug counts can be a cause of concern because they can indicate that pieces of functionality (which potentially contain bugs) are being missed. When low bug counts are encountered, management may begin to wonder about the quality of testing. This article covers techniques for dealing with low bug counts, and methods for reassuring management that coverage is being achieved.

Andrew Lance's picture Andrew Lance
Giving the Human Touch to Software

Yogita works as a QA/testing professional with Mindfire Solutions, and has written a number of articles on QA and testing strategies. Yogita is currently exploring thoughts of beauty as an area of testing and its relation to usability. Her role at Mindfire has been to implement Quality processes throughout the organization and build a dedicated testing team. The team recently published a White Paper “Porting projects: Test techniques,” downloadable from www.mindfiresolutions.com. Yogita can be reached at [email protected].

Yogita Sahoo's picture Yogita Sahoo
Avoiding the Script Cemetery

It's frightening how many companies are on their second, third, or even greater attempt to automate their testing—each time junking months or years of effort and work product. Here, test automation advisor Linda Hayes shows the way to avoid having to bury your automation project.

Linda Hayes's picture Linda Hayes
Wizardry and Requirements

Illusion and reality. Challenges and fear. These are just a few of the elements that go into requirements gathering and management. Being aware of what you know and what you don't know can ensure getting the right requirements. Read on as Harry Potter fan Becky Winant shares some insight and survival tips for requirements analysts.

Becky Winant's picture Becky Winant
Reflections on a Fable about Developer-Tester Relationships

Lee Copeland's fictional story about getting children to clean their rooms struck a chord with many of our readers, who compared it to getting developers to test their code. Here are Lee's responses to your feedback, along with a few insights about the dynamics behind developers examining their work.

Lee Copeland's picture Lee Copeland
Can You Negotiate Quality?

XP teams have the right to do their best work. On the other hand, customers have the right to specify and pay for only the quality they need. How does one reconcile two potentially conflicting points of view? Is quality negotiable? If so, how do we go about negotiating it? This paper will explore the following questions: Is quality negotiable? How can we negotiate quality? What are internal and external quality, and are either or both negotiable? What's the XP tester's quality assurance role? How far should testers go in helping the customer define acceptance criteria?

Lisa Crispin's picture Lisa Crispin

Pages

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.