Release Management
Conference Presentations
Applying Development Best Practices to Automated Testing Test automation is a specialized form of software development where executable code is produced for the validation and testing process. Many best practices have been identified to allow developers to code more quickly, efficiently, and correctly, but few test automators have adopted these practices. Learn about several of these "best practices"-including code reviews and coding standards-that can be applied to automated test development. Discover how you, as an automated test developer, can capitalize on the benefits provided by these practices. |
Andy Tinkham, Spherion Technology Architects
|
|
Scripts on My Tool Belt The aims of this presentation are to: convince you that "test automation" is more than automating test execution; show some examples of the kinds of things that can be accomplished with scripting languages, using simplified code samples; and make you aware of three different scripting languages (shells, perl, and expect). |
Danny Faught, Tejas Software Consulting
|
|
Failure of a Dot Com-A Case Study In the new economy, cliches such as "Internet time" can be disastrous. As the market emphasis shifts from first-to-market to first-to-profit, Internet start-ups are forced to scrutinize decisions which directly impact their business model. Learn the steps to failure taken by one dot-com company and the lessons learned from this failed endeavor. Explore the executive decisions made to speed time-to-market and customer acquisition, and discover how product schedules are adversely affected by attempts to retrofit an architecture and introduce tools. |
Theresa Lanowitz, Gartner Group
|
|
Establishing Best Testing Practices in Your Organization The path to best testing practices begins with communication. By building relationships with a product's key players-developers, analysts, and end users-your test team can achieve a higher level of both quality and customer satisfaction. Discover the link between effective communication and implementing critical step-by-step test processes such as test conditions, test case design, test data construction, and reporting. |
Michelle Lynn Baldwin, Booz, Allen & Hamilton
|
|
Test Progress Reporting Using Functional Readiness Are you looking for a way to effectively set the expectations of senior management? The Functional Readiness Matrix (FRM) is a decision-making tool that offers a simple way to represent test progress based on the functional areas or features of an application. By enabling the test team to track actual test progress against the implementation goals established early on, the FRM allows for the presentation of valid test metrics to management in a way they can understand. |
Robyn Brilliant, Fannie Mae
|
|
Testing in the Extreme Programming World Much attention has been given to the topic of lightweight development processes-especially eXtreme Programming (XP). Robert Martin explains the concept and significance of a paradigm that believes acceptance tests should be defined by customers, and requires developers to write the unit tests before they write the code. He then separates the difficulties from the benefits inherent in this relatively new discipline. By cutting through the controversy, he's able to address the essential issues such as environmental possibilities and the need for XP. But most importantly, he addresses the question: What is the relevance of software testing and testing professionals within XP? |
Robert Martin, Object Mentor, Inc.
|
|
The Simplest Automated Unit Test Framework That Could Possibly Work Everyone pays lip service to the importance of unit testing, but rarely do developers actually integrate unit testing into their daily routine. In the spirit of eXtreme Programming, this presentation offers a simple two-class framework for automating unit tests in three popular languages: C++, Java, and C. No GUI, no templates, just a fast and productive way of organizing and running suites of unit tests. You'll walk away wondering how you have done without this simple technique for so long. |
Chuck Allison, Utah Valley State College
|
|
Managing the Test Effort Using Requirements-Based Testing Metrics It's difficult to quantify the true state of a test effort. Often, it's measured by quantity of work combined with deadline compliance. But if this is the case, then the true level of quality remains unknown. The Requirements-Based Testing (RBT) process offers a set of metrics that can be utilized throughout the development cycle. These metrics can provide an accurate picture of the test effort at any given time. |
Gary Mogyorodi, Bit Inc.
|
|
Evolution of Automated Testing for Enterprise Systems The key to accelerating test automation in any project is for a well-rounded, cohesive team to emerge that can marry its business knowledge with its technical expertise. This session is an in-depth case study of the evolution of automated testing at the BNSF Railroad. From record-and-playback to database-driven robust test scripts, this session will take you through each step of the $24 billion corporation's efforts to implement test automation. |
Cherie Coles, BNSF Railroad
|
|
STAREAST 2001: Managing the End Game of a Software Project How do you know when a product is ready to ship? QA managers have been faced with this question for many years. Using the methodology discussed in this presentation, you take the guessing out of shipping a product and replace it with key metrics to help you rationally make the right decision. Learn how to estimate, predict, and manage your software project as it gets closer to its release date. Learn how to define which metrics to track--and how to measure them. Discover how to define the ratings scale for each metric and how to create a spider chart for product readiness. This presentation is a must for any individual or organization that is serious about maximizing the results of positive events and minimizing the consequences of adverse ones. |
Mike Ennis, BMC Software
|