Please enter an article title, author, or keyword
Birth of a Test Organization

This paper aims to identify practical, easily implemented solutions to establishing a test organization. Often testers are put in a test group that is defined in name only. Regardless of what name your organization uses for the test function, you need to determine your group's identity and what you will and will not be responsible for. I liken this process to that of the growth stages of a child from crawling to first steps to walking.

Lisa Bresko
Divide and Conquer: Making Sense Out of Test Planning

The neophyte test planner is often overwhelmed by the complexity and scope of test planning. This paper presents several practical methods for dividing the testing into manageable pieces, based on the author's experience over ten years of testing a wide variety of products.

Kathy Iberle's picture Kathy Iberle
Defect Management in Development and Test

A simple survey I have been conducting at conferences since 1994 demonstrates few organizations use defect data to manage their product development. I have asked a series of questions, and provide the results.

Ed Weller's picture Ed Weller
System Testing Strategies for Highly Available Clustered Systems

This paper focuses on the strategies and challenges of testing real-world, large and complex, highly available clustered systems in the following areas: Test planning, Strategies and methodologies; Defect tracking processes; System Configuration tests; Cluster and storage fault injection tests; Effective testing practices.

The information provided in this paper is aimed at helping test engineers understand many of the quality assurance issues involved in testing large and complex systems.

Subbarao Jagannatha
Test Planning in a Fluid Environment

As a test manager, I know the product needs to be released on schedule. I'm trying to stay on schedule, but there are changes in the software. I have to keep my test team apprised of the changes and revise the test plan…again. Now it's time to plan for the next test cycle. This article offers four keys to a successful test plan: Involvement of Test Team from the Beginning, Integration Testing, Identification of Handoff Criteria, and Interaction Among All Players.

Chris DeNardis's picture Chris DeNardis
Using GUI-based Automated Test Tools to Test Legacy Applications

A great many companies today are currently running numerous legacy (character-based or "green screen") applications on a variety of platforms (Mainframe, AS/400, Tandem, Stratus, etc.). Furthermore, there is an increasing trend toward integrating these systems with front-end GUI, Internet, and intranet applications, and using the Mainframe and AS/400 type computers for back office processing. Some companies are using AS/400s as Internet and Network servers. Most companies are opting to access their Mainframe (etc.) computers via Terminal Emulation from PC Workstations, rather than use "dumb terminals."

Keith Zambelich
Where Should Moderators Come From?

Moderators surface by "natural selection" sometimes. They are often project members whose ability to facilitate a meeting sets them apart. Sometimes they fall into that role simply because they have the most credibility, for a variety of reasons. This article explores different organizations' and different individuals' experiences in how moderators were selected for their respective projects--and offers insight into where moderators should come from.

Gerald M. Weinberg
Identifying Critical Requirements Using FMEA

Engineers in other specialties have adopted the FMEA to analyze all sorts of manufacturing processes and products. The FMEA process allows a development team to identify potential product related process failure modes and assess the effects these failures might have.

Edith Maverick-Folger
How to Write Better Test Cases

What is it worth to improve test cases? What risk would impel you to invest in better test cases? As long as they cover the software requirements, isn't that good enough? The answer to these questions is that poor test cases do indeed expose you to considerable risk.

Dianne Runnels
Using The "ICED T" Model to Test Subjective Software Qualities

Quality software—that is what we are seeking. While this is clearly a goal of any software tester or quality engineer, what exactly is the definition of quality software? Part of the answer is easy. There are many aspects of software that we can test and measure and to which we can assign a number. Some examples are how often the software crashes, how long it takes to complete a given task, or how much memory is being used. We can also look at how many of our tests pass and how many fail. While these quantifiable measures are important, they do not provide a complete picture of software quality. There are other more qualitative aspects of the software that also need to be considered.

Andy Roth


Upcoming Events

Jun 02
Sep 22
Oct 13