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
November 30, 2000 |
|
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. |
||
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; |
||
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. |
||
Model-Based Testing for Data Centric Products Data centric products such as language and language-based logic products can pose an overwhelming test problem. Here is an approach to begin defining an omniscient test suite to attack search engine bugs using model-based testing theories in the real world. |
||
Performance Testing E-Commerce Web Systems By performance testing your Web systems before they are elevated to production, you will know in advance what needs to be beefed up for the "big day." At Vanguard, our biggest day happened over the Y2K weekend when many of our clients logged in to check on their life savings. This presentation will go through how we prepared for this event and how you can do the same. |
||
Component Testing with Intelligent Test Artifacts This article presents a set of design patterns commonly encountered when creating automated test frameworks and application domain specific test cases, and introduces the notion of test artifacts as a test component architectural model for implementing those patterns. |
Michael Silverstein
November 28, 2000 |
|
Automating Software Testing: A Life-Cycle Methodology Automated Testing Lifecycle Methodology (ATLM) is a structured approach that is geared toward ensuring successful implementation of automated testing. The ATLM approach mirrors the benefits of modern rapid application development efforts, where such efforts engage the user early in the development cycle. The end-user of the software product is actively involved throughout analysis, design, development and test of each software build, which is augmented in an incremental fashion. |
||
The Automated Testing Life-Cycle Methodology (ATLM) The Automated Testing Life-cycle methodology (ATLM) summarized in this article has been adopted by various companies throughout the world. |
||
Juggling Can Improve Productivity At the 2000 Amplifying Your Effectiveness (AYE) conference I attended a class called "Being a Change Leader." One of the instructors, Sheila Smith, selected five volunteers from the audience. She told these volunteers that for this role-playing demonstration they were now her employees and she was their manager. Their company had studied and researched ways to improve productivity, and had determined that they could obtain a 50 percent increase in productivity by learning to juggle. The company was now making it mandatory for all employees to learn how to juggle. |
Todd Berbert
November 27, 2000 |
Pages
Upcoming Events
Apr 28 |
STAREAST Software Testing Conference in Orlando & Online |
Jun 02 |
Agile + DevOps West The Latest in Agile and DevOps |
Sep 22 |
STARWEST Software Testing Conference in Anaheim & Online |