STAREAST 2002 - Software Testing Conference

PRESENTATIONS

Enterprisewide Testware Architecture

Testware: the stuff of which tests are made. The term comprises a bewildering range of artifacts including data files, scripts, expected results, specifications, and environment information. It also implies how these artifacts are arranged, where they're stored and used, and how they're grouped and referenced.
Mark Fewster, Grove Consultants
Finding Firmware Defects

Embedded systems software presents a different breed of challenges to the test professional than other types of applications. Hardware interfaces, interrupts, timing considerations, resource constraints, and error handling often pose problems that aren't well suited to many traditional testing techniques. This presentation discusses some of these problems, and the techniques and strategies that are the most effective at finding software bugs in embedded systems code.
Sean Beatty, High Impact Services Inc
Four Keys to Better Test Management

Three years ago, Christopher DeNardis embarked on a career as a software tester. After just one year of testing, he was promoted to leader of the test group. In this session, he shows you the four keys to getting through those times and becoming better organized as a test manager: 1. a common set of ground rules on the test progress, defect reporting, and verification; 2. the ability to convey how your team's testing is going on a frequent basis; 3. knowing what needs to be tested and being able to stand behind the reasons why; and 4.
Chris DeNardis, Rockwell Automation
Get Real ! The Importance of Realism for Web Site Capacity Assessment

What is meant by Internet realism during load testing/capacity assessment? Part of it is understanding the importance of not only carefully characterizing the behavior of visitors to a Web site, but also the behavior of the Internet itself. Contributing to this realism are important measures such as packet loss, link speeds, millions of IP addresses, browser emulation, SSL, and other factors that can cause significant performance issues.
Philip Joung, Caw Networks
Going Beyond QA: Total Product Readiness

The successful release of software requires more than just testing to ensure the product functions properly; success is also defined by how prepared the product is for advertisement, delivery, installation, training, support, etc. In this paper, we’ll discuss how testing can be expanded to cover all aspects of Total Product Readiness (TPR).
Douglas Thacker, Liberty Mutual Insurance Group
How to Thoroughly Test Your Data Warehouse

The purpose of this paper is to describe general data warehouse structure and background, as well as specific situations encountered during the testing effort for our project. Our project was to test a data warehouse and data mart for a large research department of a pharmaceutical manufacturing company. This was a pilot project and our efforts, if successful, would pave the way for
future data warehouse projects within the company.
Suellen Arbuckle, Eli Lilly & Company and Rebecca Cooper
Identifying Testing Priorities Through Risk Analysis

It's impossible to test everything-even in the most trivial of systems. Tight time schedules and shortages of trained testing personnel exacerbate this problem; so do changing priorities, feature creep, and loss of resources. In many companies, test professionals either begin their work on whichever components they encounter first, or the parts they're most familiar with. Unfortunately, these approaches may result in the delivery of a system where the most critical components remain untested.
Rick Craig, Software Quality Engineering
Investing Wisely: Generating Return on Investment from Test Automation

Implementing test automation without following best practices and tracking your ROI is a prescription for failure. Still, many companies have done so seeking the elusive promise of automated testing: more thorough testing done faster, with less error, at a substantially lower cost. However, fewer than fifty percent of these companies realize any real success from these efforts. And even fewer have generated any substantial ROI from their automated testing initiatives.
Dale Ellis, TurnKey Solutions Corp.
Looking Ahead: Testing Tools in 2010

It's May 15, 2010, and you're in a triage meeting reviewing the testing status and bugs in your telemedical software. The system uses real-time voice, video, graphics, and an expert knowledge base to support expert medical procedures in remote locations. As the test manager, you're using trace diagrams, deployment diagrams, runtime fault injection, coverage views, test patterns, built-in self test, and other modern, agile techniques to review the bugs, diagnose faults, assign priorities, and update your test plans.
Sam Guckenheimer, Rational Software ATBU
Movin' On Up: Making the Transition from Test Lead to Manager

Want to be a test lead? Ready to take on the responsibilities of test management? Making the transition to a lead, then a management position, takes more than just guts- it takes preparation. This presentation illuminates some of the technical aspects you'll encounter when transitioning to test lead or test manager, including: organizing and managing the testing; working with the project manager and the rest of the project team; and deciding how, when, and what to invest in your test infrastructure.
Johanna Rothman, Rothman Consulting Group

Pages

AgileConnection is a TechWell community.

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