Conference Presentations

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
Explaining Testing to Anybody

Developers, management, and marketing people are clients of the testing process, but they don't know much about it. This ignorance of testing can often lead to decisions that make it harder for testers to do good work. That is why it is helpful to have rapid ways to explain testing issues. Hear some general "three-minute analogies" and "elevator speeches" that will help you explain why testing can be so time-consuming, difficult, and uncertain.

James Bach, Satisfice, Inc.
Outsourcing the Software Testing Effort: A Negotiating Checklist

This presentation raises several of the issues involved in partial or complete outsourcing of the software testing effort. Attorney Cem Kaner presents his negotiating checklist, including how to evaluate the costs, benefits, and risks of test outsourcing. Learn how to effectively use an outsourcer's staff with your testing projects.

Cem Kaner, J.D., Ph.D., Florida Tech
Manage Testing by the Numbers

Telcordia's Software Quality Assurance Testing Organization Business Model was developed to assist its SQA Testing Management Team in becoming more effective and productive in managing SQA testing. Learn how the implementation of this model can help raise the overall technical expertise of your test management team.

Sharon Burrell, Telcordia Technologies
Trimming the Test Suite: Using Coverage Analysis to Minimize Re-Testing

Coverage Analysis System (CAS) data is often useful in determining that enough tests have been written, and identifying C-code lines that have no test coverage. In this presentation, Jim Boone explores various methods that use CAS data to determine the best set of automated tests to execute for a corrected defect. Learn the strengths, weaknesses, and best stage for using each method.

Jim Boone, SAS, Institute, inc.
Equilibrium in Managing Outsourced Testing

Even organizations with internal QA departments often have to rely on outsourced testing resources for some jobs. The first time you do this, you may make a lot of mistakes as well as learn a great deal. Jeff Jewell relates the lessons learned from his company's first experience in managing a project with contract testers. Learn what you can do to get the most from external testers and ensure that the quality of the product meets your internal expectations.

Jeff Jewell, Navigant International Inc.
Test Metrics Without Tears

The profile of testing has been raised significantly in the last few years, largely due to Year 2000 issues. Organizations accept that they need to systematically and thoroughly test software, and they are demanding the same levels of efficiency that are expected from all other areas of their businesses. Now it is necessary to provide evidence that the activities of the test team are an effective and efficient use of staff. Learn how such evidence can be obtained and reported with minimal overhead on testing resources.

David Vaughan, The SIM Group
Improve Your Estimating Process--Beginning with a Proof of Concept

Estimating is like the weather; everyone talks about it, but no one does anything about it. This presentation provides the techniques required to execute a Proof of Concept estimating model, allowing an organization to trial run the tools, techniques, and methods required to estimate projects more accurately and earlier in the lifecycle. Learn the key elements of this approach, and obtain templates to employ in your organization.

David Herron, The David Consulting Group, Inc.
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. Or, at the very least, critical components are tested later in the lifecycle when there may not be time to fix the problems found. All of this adds to the risk of a project. One way to overcome every one of these challenges is to employ the use of risk analysis. Rick Craig demonstrates the basics of a usable process for assigning testing priorities based on relative risk.

Rick Craig, Software Quality Engineering

Pages

CMCrossroads is a TechWell community.

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