|
End the Guessing Game - Regression Test Selection Methods Developing your regression test suite does not have to be a guessing game. Impact analysis offers a detailed, code-based, regression test selection process to determine what areas of a software program need-and which do not need-to be re-tested. This approach produces big reductions in the amount of regression testing required. Brian Robinson discusses regression test selection principles, change determination, impact analysis of changes and tests, test selection or creation, and automation tools. When a bug escapes your regression tests, learn how to improve your process and prevent this type of bug from returning. Brian shares the results using regression test selection methods at ABB where they achieved an average of 40 percent savings in time and a 35 percent increase in defects detected.
|
Brian Robinson, ABB Inc.
|
|
Let's Make Bugs Miserable Preventing and eliminating bugs is what quality is all about. Help! Call the virtual exterminator! From the moment a bug is created until it is killed or morphs into another bug, it goes through many stages in its "life." Anibal Sousa discusses what can be done to shorten a bug's life and offers a manageable bug-handling process, which can be used to track, prioritize, inspect, catalog, and fix bugs safely. A test manager at Microsoft, Anibal discloses best practices and recommendations for preventing simple bugs with check-in test and auto-daily builds with test automation, creating a bug database system, prioritizing and evaluating bugs correctly, killing the bugs and their siblings for good, and more. Let's make a bug's life miserable!
|
Anibal Sousa, Microsoft Corporation
|
|
Quality Assurance and Testing in an FDA Regulated Environment How can we reduce costs associated with FDA imposed computer systems validation (CSV) guidelines and improve test coverage at the same time? Experienced in the use of automated testing tools in FDA regulated environments, Eric Toburen shares the challenges of complying with FDA validation guidelines. For many companies, manual CSV is a like a heavy boat anchor that slows projects and increases costs while adding no value other than the perception that the practice avoids an auditor's attention. Find out how automated testing and test management practices can be used to shorten the CSV lifecycle and improve test coverage. After deployment use the automated tests for regression testing to enable the deployment of bug fixes and upgrades minimizing the need for re-evaluation.
|
Eric Toburen, Genilogix
|
|
Diagnosing Performance Problems in Web Server Applications Many application performance failures are episodic, leading to frustrated users calling help desks, frantic troubleshooting of production systems, and re-booting systems. Often these failures are a result of subtle interactions between code and the configuration of multiple servers. On the other hand, well-designed applications should demonstrate gradual performance degradation and advanced warning of the need to add hardware capacity. Join Ron Bodkin as he discusses the patterns of application failure, some common examples, and testing techniques to help reduce the likelihood of episodic failures in production. Learn about the tools and techniques needed to instrument the application, monitor the infrastructure, collect systems data, analyze it, and offer insight for corrective actions.
|
Ron Bodkin, Glassbox software
|
|
Testing Web Services Security Many organizations are beginning to deploy Web services as the preferred way to interact electronically with employees, customers, and trading partners. To ensure that these Web services implementations are secure, vulnerability assessment and rigorous testing must be built into the Web services development process. Jack Quinnell describes the current "best practices" in developing and testing the security of an enterprise's Web services applications. He explains what makes Web services vulnerable to attacks and the characteristics of both design-centric and attack-centric vulnerabilities. Learn how to identify and test these vulnerabilities during development and in operational settings. Find out about the latest technology to support testing Web services security. Go away with a new appreciation for the security risks inherent in Web services and what you can do about them.
|
Jack Quinnell, Kenai Systems
|
|
STARWEST 2004: Testing Dialogues - Management Issues Many organizations are beginning to deploy Web services as the preferred way to interact electronically with employees, customers, and trading partners. To ensure that these Web services implementations are secure, vulnerability assessment and rigorous testing must be built into the Web services development process. Jack Quinnell describes the current "best practices" in developing and testing the security of an enterprise’s Web services applications. He explains what makes Web services vulnerable to attacks and the characteristics of both design-centric and attack-centric vulnerabilities. Learn how to identify and test these vulnerabilities during development and in operational settings. Find out about the latest technology to support testing Web services security. Go away with a new appreciation for the security risks inherent in Web services and what you can do about them.
|
Facilitated by Esther Derby and Elisabeth Hendrickson
|
|
Testing with the Open Source DBUnit Framework Many enterprise applications are tightly coupled to a database. Consequently testing application code that depends on a database is challenging because the act of testing changes the database, often making retesting a problem. When it comes to white box testing, databases present dependency scenarios that are sometimes difficult to set-up. Fortunately, the open source DBUnit framework, which employs XML datasets, provides an elegant solution for controlling database dependencies within applications. It allows both testers and developers to set the state of a database at the beginning of the test and to place the database back into its pre-test state upon completion. Andrew Glover demonstrates component and system testing scenarios using the DBUnit framework and discusses the issues and solutions for database dependent applications.
|
Andrew Glover, Vanward Technologies
|
|
Testing Windows Registry Entries Warning: Registry keys may be hazardous to your program's health! Registry key entries in Windows applications-visible or hidden-are often neglected by testers. A registry key entry is a program feature just like any other application function and as such needs to be validated. Michael Stahl describes why registry keys should be accorded special attention during testing and proposes a strategy for mitigating risks posed by incorrect registry key entries. He suggests a test strategy, as well as coding standards for input value and type validation, default values, regeneration, and naming rules. Michael demonstrates the use of correct and incorrect registry keys in common commercial applications.
|
Michael Stahl, Intel Corporation
|
|
Performance Testing Early in Development Iterations When the software architecture is emerging and many features are not yet ready, performance testing is a challenge. However, waiting until the software is almost finished is too risky. What to do? Neill McCarthy explores how performance testing can be made more Agile and run starting in the early iterations of development. Learn how to implement early performance automation using appropriate tools in build tests and the requirements for early performance testing of user stories. Neill presents lessons learned from his "coal face" of performance testing in Agile projects and shares ideas on how you can add more agility to your performance testing.
|
Neill McCarthy, BJSS
|
|
Security Nirvana - Combining Source Code Scanning and Penetration Testing Penetrate and Patch. That's the unspoken model that many software development teams have been following for the past several years: build it, and when a security problem is found, then scurry around to patch it. We now know that the cost of building software this way is orders of magnitude more expensive than ingraining security throughout the development lifecycle. Ady Kakrania walks through the process of building security into your development process from the design phase and continuing good software security practices post-deployment. Learn about synergistically using tools like source code scanners to find dangerous functions and structures along with post-deployment penetration testing to dramatically reduce costs and shore-up your application's security.
|
Ady Kakrania, Security Innovation LLC
|