|
|
Confessions of a Modeling Bigot Migrating a testing infrastructure from data-driven test automation to a model-driven test architecture, including the need to maintain backward compatibility was a huge challenge for Michael Corning and his groupx0151but a very rewarding one. The test group manages three modeling tools supporting both state-based and grammar-based modeling techniques. Modeling became important and ultimately indispensable not only for product testing but for the test infrastructure development as well. The results can be programs that are self-documenting and virtually self-testing.
|
Michael Corning, Microsoft Corporation
|
|
|
A Test Strategy For Web Services What are Web services and why should you care? Web services offer companies the opportunity to deliver applications that are not feasible with traditional approaches. Learn how businesses are using Web services today and how they interact in the network. Alan Newman provides a customized test methodology for applications employing Web services functionality. Take away a new awareness of the challenges for testing this technology and a strategy for defining the scope of testing Web services.
|
Alan Newman, Spirent Communications
|
|
|
Attacking GUI Test Automation Maintaince Headaches GUI-centric automation scripting is a major cause of the high costs and failed test automation efforts. These scripts may work fine for one release, but quickly break down when the GUI changes, triggering huge maintenance efforts resulting in ultimate failure. Based on the successes at CISCO, Jeff Feldstein discusses the ways they have mitigated these problems with: back-end testing without the GUI; using appropriate manual testing; simulating browsers with HTTP proxy software; and many more tricks-of-the-trade.
|
Jeff Feldstein, Cisco Systems Inc
|
|
|
Building An Enterprise Test Lab An enterprise test lab provides a stable, independent testing environment that leverages your investment in equipment, software, and people. These labs are often built without an analysis of the architecture needed for an effective test lab. Learn how to build or improve your enterprise test lab and make it more adaptable without large investments in time or materials. With an enterprise test lab in place, you can improve the reliability of the end-to-end user experience in production and reduce overall costs at the same time.
|
Alan Forand, EDS
|
|
|
Testing Dynamic Web Applications With Usage Models Markov chain usage models provide significant automation capabilities, including test case generation, test execution, and result analysis. Kirk Sayre presents a real-world case study describing how Markov chain testing techniques were applied to the testing of dynamic Web applications. Learn how Markov chain models are used to generate random and non-random test and provide you with reliability and risk estimation information. Use this technique for load and performance testing, system testing, and acceptance testing.
|
Kirk Sayre, The University of Tennessee
|
|
|
Testing Beyond Section 508 Compliance for Accessibility In the software and Web site testing arenas, you must evaluate your commitment to Section 508 compliance, as well as the accessibility of products and applications to people with disabilities. Juanita Fischer presents testing techniques and processes you can use to ensure that your product or Web application is accessible to everyone, not just Section 508 compliant. Learn how to evaluate your Web application against the sixteen Section 508 standards and various assisstive technology (AT) tools for disabilities including hearing, vision, cognitive, mobility, and seizure disorders.
|
Juanita Fischer, Joint Interoperability Test Command
|
|
|
Automated Testability: The Missing Link in Test Automation Many organizations invest in test automation tools that become "shelfware." One answer is automated testabilityx0151how well an application supports the implementation, execution, and maintenance of automated testing. John Fodeh explains how the quality of an applications automated testability is defined by control; visibility; consistency; reliability; persistence; and documentation. Learn ways to improve automated testability during the early design stages of the application to dramatically increase your test automation success. Plus, find out how to improve automated testability in your current applications.
|
John Fodeh, B-K Medical
|
|
|
Ensuring Requirements Traceability in Functional and Performance Testing If written requirements are important in your development process, then requirements traceability is a key to ensuring quality in your testing process. For you, every test plan should include traceability for both functional and performance testing. Learn about the sources and characteristics of good requirements and how to perform requirements tracing on your project. Develop a Requirements Traceability Matrix (RTM) for both functional and performance testing requirements. For even better results, integrate requirements traceability into your requirements management process.
|
Marc Bloom, Capital One Financial Corp
|
|
|
Increase the value of your testing with Business-oriented metrics Business-oriented metrics can bridge the gap between the activities your testing organization perform and the business value your testing produces. Claude Fenner presents real-world examples to motivate and show you how to successfully communicate the strategic value of what you do in your test organization. Learn how the Test Asset Trajectory metric shows testing's fit-to-business demand and whether or not your testing assets are healthy. With the Test Asset Leverage metric, you can better communicate the total cost of ownership and efficiency of your testing assets. Use this information within your own test group to benchmark the current status and map out ways to progress to the next level.
|
Claude Fenner, Arsin Corporation
|
|
|
Security Testing Web Applications Often, the fast-paced development cycles of Web applications don't usually leave much room for testing. Thanks to the instant service pack phenomenon, we can update a Web application every day-so it's ok if things aren't perfect, right? That may be the case for functional bugs, but not security bugs. All an attacker needs is a very small window of opportunity to do damage. James Whittaker shows you how to identify these threats and demonstrates examples of attacks against them. From "SQL injection" to "cross-site scripting," and many more, you’ll leave with the knowledge of how a hacker views your online business and, as a tester, what you can do about it.
|
Dr. Mike Andrews, Florida Institute of Technology
|
