|
|
Implementing an Automated Regression Test Suite Many efforts to automate regression testing have failed or not met expectations-resulting in "shelfware." Lloyd Roden presents a real-world case study based on the success of implementing a regression test tool within a software company. Learn the steps taken in evaluating and deploying the tool. Discover the key benefits and successes achieved over a three-year period as well as the challenges faced while using the tool.
|
Lloyd Roden, Grove Consultants
|
|
|
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
|
|
|
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
|
|
|
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.
|
|
|
Targeted Software Fault Insertion Since the completely random software fault insertion techniques suggested in much of the research literature are not practical for most software products, this paper suggests that a modest targeted software fault insertion effort for a few common error conditions can have a dramatic impact on defect detection rates and quality. The paper uses the example of a software fault insertion subsystem, codenamed Faulty Towers, which was added to Mangosoft Incorporated’s test automation in order to target
common failures and errors.
|
Paul Houlihan, MangoSoft Corporation
|
|
|
White-Box Testing: What Your Developers Don't Want You to Know In this presentation, John Peraza describes how to use white-box testing to discover those defects that would otherwise remain undetected if you only conducted black-box testing. Learn various techniques-including test coverage, run-time memory leak detection, dynamic bounds checking, and code assessment for internationalization-that you can use to conduct white-box testing. Discover how BMC Software has benefited from including white-box testing in its quality assurance efforts.
|
John Peraza, BMC Software, Inc.
|
|
|
Succeeding with Automation Tools The problems with using record/playback as your only test automation strategy are well known. But the other option-full script programming-is unattractive to many due to its high cost and long development time. This presentation discusses a strategy called defensive programming that incorporates the best of both worlds. Learn how to leverage your automation tool with simple implementation techniques to create robust test suites.
|
Jamie Mitchell, BenchmarkQA
|
|
|
Thinking About People, Process, and Product: A Principle that Works at Work All projects involve the three P's: people, process, and product. People includes everyone who influences the project. Process is the steps taken to produce and maintain software. Product is the final outcome of the project. To keep these three in harmony, you must observe who is trying to do what to deliver what. Usually, two of the three P's are mandated, and the third one is chosen appropriately. Although this is common sense, it is not common practice. Dwayne Phillips discusses the issues and challenges that affect us all on every project. Learn about the ideas and questions to consider to help you work through these issues.
|
Dwayne Phillips, U.S. Department of Defense
|
|
|
Predictive Metrics to Estimate Post Project Costs How much will it cost to support your software project based on current estimations? Discover the answer to this question by using statistical estimation methods-including the S-curve and the Rayleigh curve-to help you determine where your projects are in relation to required quality and trendings to meet your post-project cost goals. Learn how to use metrics to predict post-project costs and make better release decisions based on these predictions.
|
Geoffrey Facer, Intel Corporation
|
