The Latest

Using The "ICED T" Model to Test Subjective Software Qualities[article]

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
What Do You Manage?[article]

You're a test manager. But do you manage only the testing? A frustrated test manager recently said, "With my SQA hat, I want to focus on finding defects and discovering risk in the product. With my support hat, I want to solve problems. With my tech pubs hat, I'm trying to get the documentation written. But last week, everyone needed my help at once. I'm only one person—how the heck do I do all that?" Well, maybe you shouldn't have to.

Johanna Rothman's picture Johanna Rothman
Design Thinking Design Thinking: 4 Steps to Better Software[article]

Design thinking points out several missed steps in software development. And, while some may believe ideation and iteration to be wasteful, they're easy to add to the development process at low cost and, in the end, result in substantially more valuable software. In this article, Jeff Patton describes the four basic steps of design thinking.

Jeff Patton's picture Jeff Patton
You Want It When?—Negotiating Test Schedules[article]

The biggest obstacle in the software industry is lack of time to do the job well. Negotiation can buy valuable time and help management avoid blunders. This paper is about estimating and negotiating test schedules.

Gregory M. Pope
Why Software Fails (And How Testers Can Exploit It)[article]

This paper summarizes conclusions from a three year study about why released software fails. Our method was to obtain mature-beta or retail versions of real software applications and stress test them until they fail. From an analysis of the casual faults, we have synthesized four reasons why software fails. This note presents these four classes of failures and discusses the challenges they present to developers and testers. The implications for software testers are emphasized.

James Whittaker's picture James Whittaker
Testing Java Virtual Machines[article]

In this paper, the authors describe their experience with automatically testing Java virtual machines and describe two specific techniques for generating test cases.

TechWell Contributor's picture TechWell Contributor
Planning and Managing Complex Test Resource Logistics[article]

Subtle but catastrophic bugs, such as those that cause server crashes and database record-lock race conditions, often only reveal themselves during performance, stress, volume, data quality, and reliability testing. Such testing is most effectively performed in test environments-hardware, software, network, and release configurations-that mimic as nearly as possible the field environment, because test results in less-complex settings often do not extrapolate due to the non-linearity of software. In complex settings, such as Web and e-commerce server and database farms, managing these lab configurations can be quite challenging. This paper presents a basic Access database, designed using the Entity-Relationship technique, that will allow the Test Manager to plan, configure, and maintain this test environment through the test project.

Rex Black's picture Rex Black
Three Keys to Test Automation[article]

How can you get your test automation project off on the right foot? I've been asked this question many times. It has prompted me to review the test automation projects in which I've been involved and identify the factors most associated with success.

Bret Pettichord's picture Bret Pettichord
Process Enhancement Request Form and Procedures (template)[article]

The PERF (Process Enhancement Request Form) template was created to promote continuous process improvement. Anyone in the organization can submit a PERF to add, change, or remove anything having to do with processes.

TechWell Contributor's picture TechWell Contributor
Use Your Mainframe to Test[article]

As testers we typically receive software from a development group at the end of the build cycle and then install this software into a given test system. We then run a set of pre-written test cases that exercise the software in a way that tests the software in a simulated environment. These tests generally take one of 3 forms. 1) We examine manually or programmatically the UI screens that the software produces. 2) We test the objects and methods of those objects in the program by exercising test code that interacts with the product code. 3) We do a "System Test" or black box test that places the product in a simulated user environment and then we do the operations that an end user would and verify the results.

TechWell Contributor's picture TechWell Contributor
Creating a Test Plan Database for Standardized Tests Across Multiple Nodes[article]

This paper accompanies a STAR presentation that takes the participant on a journey through the long-term effort to transform a manual test-tracking approach to a database-drive approach.

TechWell Contributor's picture TechWell Contributor
Bug Reports That Make Sense[article]

After a defect has been found, it must be reported to development so that it can be fixed. Much has been written about identifying defects and reproducing them--but very little has been done to explain the reporting process and what developers really need. This paper is to provide a guideline for what information should be included in a report and how the information will vary based on the type of bug and the type of function.

Mary Decker
Better Test Cases Through Improved Testability[article]

This paper defines testability and discusses its importance for software applications. We take a look at why it gets left out of most software components and why it needs to be there right at the design stage of the software development life cycle. It also examines common software controls from a testability point of view and suggests improvements that should be made to ensure better testability.

TechWell Contributor's picture TechWell Contributor
Testing Initiatives at the New York Stock Exchange[article]

Three years ago, the NYSE and SIAC established an initiative to improve the productivity and quality of testing. This paper discusses the key architecture and infrastructure elements of that initiative including: The suite of tools needed to test and control 20 major software systems that are written in many different computer languages, operate on heterogeneous  hardware platforms and operating systems, and are in a constant state of change;
The development, operation, and maintenance of robust, reusable business-oriented Regression Scripts; Key issues and lessons learned.

TechWell Contributor's picture TechWell Contributor
Successful Test Management: 9 Lessons Learned[article]

Many test managers came to management through the technical ranks. Although they may have had plenty of testing and/or engineering training and mentoring, they frequently learn management skills the hard way, through trial and error. This article describes some of the lessons Johanna Rothman has learned about managing testing teams.

Johanna Rothman's picture Johanna Rothman


StickyMinds is a TechWell community.

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