|
Smarter Testing with the 80:20 Rule It may not be a silver bullet, but knowledge of the 80:20 rule, and the special variation that applies to software testing, can help you dramatically improve your testing-and your entire software development lifecycle. This session explains what the rule is using real-life examples, then shows you how to use it within your test team. Erik Petersen then investigates the different ways the rule is being used by leading testers and developers today. This talk has motivated some Australian testers to change the way they test. Will this approach from Down Under turn your testing ideas upside down?
|
Erik Petersen, Specialist
|
|
Testing a Distributed Application Written in Embedded Windows CE How will your Windows CE application perform once you start deploying it in the "real world"? This session addresses the many issues developers face when building distributed applications using embedded Windows. The ability to set up your application simulating the "real world" in a controlled lab environment using automated testing tools-along with the option to troubleshoot-saves critical time and money. Don't forget to be aware of the many pitfalls you face. You must also identify tools and strategies to resolve your product's problems before they impact your company's "real" customers.
|
Jim Walters, BSQUARE Corporation
|
|
Testing for Section 508 Accessibility Compliance Section 508 of the Rehabilitation Act is a key issue affecting testing for more and more companies. Section 508 requirements include a set of Web design guidelines that allow users with various disabilities to more easily access information from the Web. Adoption language by the federal government in June 2001 stated that all federal agency Web sites must be 508 compliant-but the push for accessibility is spreading to state government and the private sector as well. Bill Chandler covers who's expected to become compliant, when you'll need to be compliant, and how to find out your current level of accessibility. Learn to leverage existing tools and processes to test the accessibility of your Web site and make the necessary changes. Plus, figure out how Section 508 will affect your future development processes.
|
Bill Chandler, Rational Software
|
|
Laws of Testability This presentation explains the four "laws" of testability: test automation isn't possible without some level of testability; test automation is most successful when developers focus on providing testability; there is no clear distinction between automation support and testability features; and automated tests are never completely realistic. It also describes the characteristics of "testability."
|
Bret Pettichord, Pettichord Consulting
|
|
STARWEST 2002: How to Break Software Security This presentation addresses classifying, finding, and attacking software security vulnerabilities.
|
James Whittaker, Florida Institue of Technology and Herbert Thompson, System Integrity
|
|
Keeping Your Outsourced Testing Under Control As companies focus on their core business, the option to outsource software testing becomes more and more attractive. And there are plenty of organizations out there that specialize in the practice. But implementing outsourcing can feel like an uncertain proposition. In this session, Martin Pol explains how you can effectively select, implement, and audit outsourced testing activities. He shows you step by step what needs to be done to make outsourcing work for you and your company.
|
Martin Pol, POLTEQ IT Services BV
|
|
How to Avoid Adaptive Testing Syndrome Adaptive Testing Syndrome happens when, for various reasons, test team members become blind to the idiosyncrasies of the software and even accept them as a normal part of the design. However, when a different tester, or maybe just a different set of tests, comes in contact with the software, the bugs become painfully obvious. Here's how to diagnose and avoid ATS.
|
|
|
Karl Wiegers on Software Inspections and Peer Reviews Peer reviews and inspections are among the highest-leverage software quality practices available. Here are some useful sources of guidance on how to perform software inspections and peer reviews, as well as some tools and online resources that can help you jump-start your fledgling review program.
|
|
|
Bypassing the GUI Graphical User Interfaces make test automation hard. The problems are well known. You need specialized tools to drive the GUI. Those tools can be confused by the common programming practice of inventing custom user interface controls. When they are used in the simplest way, the tools lead to fragile tests that tend to break en masse when the GUI changes. Making the test resistant to change requires elaborate and sometimes awkward testing frameworks. Learn how to use a scripting interface to get around the GUI problem.
|
|
|
A Picture's Worth a Thousand Words Maps are a universal way of describing an area. You use them to plan your route and find your destination. Just as it's a good idea to have a map when traveling, it's a good idea to have a picture of the software you're testing. Elisabeth Hendrickson describes UML, parts maps, flow charts, state diagrams, and more.
|
|