Conference Presentations

Writing Testable Use Cases

Use cases are hard to test because they do not have a standard format or style, and lack coherent structure. This is due in part to the need for a standard definition in UML, which defines the graphical part but not the textual part. In this session, Jim Heumann pinpoints the issues related to testability of use cases and introduces a testable style for writing use cases, a process used extensively and successfully by IBM Rational Software. Based on the testable use case writing technique, you will learn how to create test cases from these use cases.

  • How to make a use case more understandable and testable
  • Examples of testable use cases
  • How to create test cases from use cases
Jim Heumann, IBM Rational Software
QA Preventing Failure Suffering for Success

One of the most valuable services a QA group provides is preventing failure. Ironically if the group succeeds at this, QA might find themselves unpopular or out of a job. Linda Hayes reveals how typical methods of measuring success can actually cause failure. Especially if success is achieved at the loser's expense.

Linda Hayes's picture Linda Hayes
Not a Game of Random() Chance

Online gaming poses a myriad of security risks. These hazards include various forms of player cheating and the possibility of unfair gaming software, in addition to the risks normally associated with any e-commerce business. Matthew Schmid describes a specific design flaw in an online poker game.

Matthew Schmid
The Top 13 Mistakes In Load Testing Applications

This is a no-holds-barred discussion of common load testing errors and consequences. Load testing can and should be done long before a system has a stable or complete user interface. One reason that people often schedule load testing as a final step in a test or development plan is the confusion linking load testing with functional testing.

Mark D. Anderson
On-Track Requirements: How to Evaluate Requirements for Testability

Prior to using the requirements to develop the Test Plan, an analysis should be performed to evaluate the testability of the requirements. This article suggests a proven method used on a recent project that accomplishes such an evaluation.

Rodger Drabick
The 11th Hour

Testers are often on the critical path for getting a software release out. They must plan carefully in order to minimize the critical path, while still doing a complete job of testing. This schedule pressure is taken to an extreme when a production server must be taken offline in order to deploy the software, and everyone is waiting for the final test results before the system can go live again. Karen Johnson describes her company's carefully planned and orchestrated method for doing a final check of an installed system. Her story is relevant to e-commerce companies as well as IT shops that are under pressure to keep systems updated while minimizing downtime.

Karen N. Johnson's picture Karen N. Johnson
Software Development Lifecycle: Defect and Test Case Measurement

This article focuses on how to manage the defect and test case measurement during the software development lifecycle. This should be a practical resource for software developers and project managers.

Steve Miller

Pages

CMCrossroads is a TechWell community.

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