|
|
STAREAST 2000: Confessions of a (Recovering) Coding Cowboy The battle lines are drawn, it seems, between programmers and testers. Do you wonder what makes some programmers so opposed to process control? Why do programmers seem to resent testers? And, more importantly, what can we do to bridge the gap? Learn how to identify different types of developer personalities and development styles and deal with them to your advantage. Susan Joslyn explores ways to inspire quality (recovery) in coding cowboys while minimizing clashes. Discover your own twelve step program to recovery in your relationships with your developers!
|
Susan Joslyn, SJ+ Systems Associates, Inc.
|
|
|
The Tester's Triad: Bug, Product, User Good testing does not come naturally to everyone. For these individuals, the best option is to look closely at really good testers and observe what often seems to come easily and unconsciously to them. Brian Marick explores how good testers make effective and efficient use of three sources of information: past bugs and their fixes; informal descriptions of the product architecture; and characterizations of the end user. Learn how good testers gather this information, and what they do with it once they have it.
|
Brian Marick, Testing Foundations
|
|
|
An Application Program Interface (API) Testing Method Discover a technique to test APIs that combines aspects of two published software testing methods: Markov modeling and category partitioning. An example is given that demonstrates this hybrid technique. Two case studies-one performed under laboratory conditions as proof-of-concept and the other on a large API-illustrate this technique's effectiveness.
|
Alan Jorgensen, Advanced Engineering Technology
|
|
|
Best Practices in Testing an Enterprise Class E-Commerce Application With nearly two hundred million people surfing the net worldwide, businesses engaged in e-commerce must use sophisticated testing techniques to guarantee the optimal user experience. If your site crashes, the downtime will cost you more than dollars! Based on Nationwide Insurance systems' best practices, this presentation will cover the entire project lifecycle of testing an enterprise class e-commerce application.
|
Jennifer Cuenot, Nationwide Insurance Systems
|
|
|
Unified Modeling Language (UML) and Testing The Unified Modeling Language (UML) has become the industry's standard for capturing software architectures and elaborating system design. This presentation provides an overview of the UML from a tester's perspective. Learn how UML represents software design, including key diagrams. Discover when these diagrams are appropriate, what information can be derived from them, and what types of software can be represented. Explore ways to use UML to facilitate communication among testers, developers, and analysts in your organization.
|
Sam Guckenheimer, Rational Software
|
|
|
Mutating Automated Tests Most automated tests are used as regression tests-doing the same exercises each time the test is run. Douglas Hoffman describes a different type of automated test-one that does something different each time. Learn how this powerful type of automated test can result in better test coverage and detection of more defects. Explore the pros and cons for mutating automated tests drawn from the presenter's work experience and real-life examples.
|
Douglas Hoffman, Software Quality Methods, LLC
|
|
|
Experiences Testing E-Commerce Systems Developing, implementing, and running e-commerce systems really does require a fresh look at how testing assures product quality, contributes to project success, and maintains a quality product during live running. Based on case studies and real-world experiences, Bob Bartlett explores the different considerations to take into account when testing e-commerce systems and the key techniques that have proven useful.
|
Bob Bartlett, The SIM Group
|
|
|
How to Break Software Applications: A Case Study James Whittaker took a group of untrained (and untainted) college students, ran them through a rigorous testing boot camp, and then pointed them at an already tested, world-class software product. Their mission: test it, break it, prove it works, and then automate everything you did. The outcome: interesting bugs, cool test automation, compelling test patterns, and useful ways of testing that you might never have considered before.
|
James Whittaker, Florda Tech
|
|
|
Test Strategy, Test Plan, Test Cases: What's the Difference? Test engineers are often asked to create a test plan for a product. Once the goals of the test project are defined, a test strategy needs to be developed. The second step is to create a test project plan to implement this strategy. A third and final step is to create the actual test case according to the test project plan and test strategy. Learn how these three components-both singularly and collectively-can contribute to a successful test project.
|
Howie Dow, Compaq Computer Corporation
|
|
|
Automated Testing of Web Content Tailored for Pervasive Devices With the emerging presence of pervasive computing devices across many market segments, and the corresponding growth in Web content tailoring, the need exists for automated test methodologies to verify tailoring engines and delivery systems. Learn methods used to quickly verify software quality through simulation of pervasive devices and programmatic verification of tailored Web content. Examine highly effective and repeatable test scenarios that have been constructed using the systems and methods described.
|
Samuel Camut, IBM
|
