|
|
STARWEST 1999: Confessions of a (Recovering) Coding Cowboy If you sometimes feel that programmers seem to resent testing, then this presentation is for you! Learn how to identify different types of programmers' personalities and development styles and deal with them to your adventage. Susan Joslyn will show you how to capitalize on these different personality types to encourage development level testing and positive response to a tester's feedback.
|
Susan Joslyn, SJ+ Systems Associates, Inc.
|
|
|
Testing Interactions in Object-Oriented Software At each level of integration (class, component, subsystem, and system), there are possible interactions between the pieces that are being integrated. John McGregor presents two techniquest to use consistently at each of the levels of integration to locate faults due to incorrect interactions. Learn how an interaction matrix and a statistical sampling technique provide a complement to the standard functional and structural test case design strategies.
|
John McGregor, Software Architects
|
|
|
STARWEST 1999: How Testers Can Contribute to Reviews and Inspections Brian Lawrence begins his presentation with a brief overview of what inspection is and how it works in software organizations. Although testers may or may not understand source code, they can still contribute considerable value in reviews. Learn how to devise tests as a review preparation technique that can identify potential defects and serve as a basis for test planning and design.
|
Brian Lawrence, Coyote Valley Software
|
|
|
Birth of a Test Organization Discover how a new test group becomes respected within an existing IT infrastructure. Learn how to crawl, take your first steps, and walk before attempting to run. Lisa Bresko discusses approaches such as her "Hugs for Bugs" campaign that helped build cooperation with applications development.
|
Lisa Bresko, Infoworks
|
|
|
A Baker's Dozen Questions to Ask Before Writing a Test Plan Have you ever needed to generate a test plan for a project or product you knew little about? Have you ever felt grossly unprepared when starting a testing project? If so, this presentation will help you. Howie Dow presents thirteen questions to help evaluate test readiness. Learn when and how to answer these questions before starting a test plan.
|
Howie Dow, Compaq Computer Corporation
|
|
|
How Testers Can Use a Software Reliability Engineering Maturity Model If you are a novice to the process of software reliability engineering (SRE) or a seasoned practitioner trying to increase efficiency, John Musa can help you! Based upon a new format, this discussion will give you a quick summary picture of SRE, showing the relationships between the level of SRE Maturity and both the efficiency of your testing process and confidence in your product's reliability. Learn how to apply the SRE Maturity Model for self-assessment of projects. Discover how to use this powerful tool to make testing more efficient.
|
John Musa, International Consultant
|
|
|
Building a Responsive Testing Team Where do you begin when building a testing team? Who should you look for and what personal skills and qualifications should they have? How do you keep testers once you get them? Obviously there are many views and opinions on this topic, some of which are often off the mark. Jack Cook examines these questions and more while providing you with a good set of answers. Whether you are a test manager, test coordinator, or test practitioner, this presentation will assist you in building a responsive testing team within your own organization.
|
Jack Cook, Qwest Communications International, Inc.
|
|
|
Five Reasons Why Your Inspection Program May Fail We've all heard that inspection is one of the best ways to improve quality and productivity, yet in our industry, sustained consistent usage of inspection has been elusive. Why is inspection so hard to get going and still harder to keep going? There are five conditions that must be present to build and keep an inspection program.
|
Brian Lawrence, Coyote Valley Software
|
|
|
Automation in Web Testing Observe how one company developed a comprehensive testing suite for a Web site that included functional, integration, and stress testing. Reinhard Weiss highlights his experiences in this project and discusses the Web development details that can radically improve your Web site's testability.
|
Reinhard Weiss, Further Inspection
|
|
|
Should This Test Be Automated? For the decision to automate a test to be a good one, the value of re-running the test must exceed the cost to automate it. People often measure value and cost in the wrong terms. In this double-track presentation, Brian Marick contends that value is not ease of execution, but the likelihood of finding future bugs. And cost is not time spent automating, but rather the manual tests that will never be run.
|
Brian Marick, Reliable Software Technologies
|
