Articles

Please enter an article title, author, or keyword
Testing Java Virtual Machines

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

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

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)

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

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

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

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

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

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

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

Pages

Upcoming Events

Apr 19
May 03
Jun 07
Oct 04