|
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
|
|
Automation Opportunities: Finding the Sweet Spot in Your Project In any test automation effort, there are "sweet spots," points of leverage where you get more for your automation efforts. Knowing how to find that sweet spot helps you determine how to spend your limited time and resources to your best advantage. In this presentation, Elisabeth Hendrickson explores various ways to find the sweet spots in your project. She uses real-world examples of sweet spots from past projects to illustrate.
|
Elisabeth Hendrickson, Quality Tree Consulting, Inc.
|
|
Seven Steps to Test Automation Success Test automation raises our hopes yet often frustrates and disappoints us. Although automation promises to deliver us from a tough situation, automating implemented tests can create as many problems as it solves. The key is to follow the rules of software development when automating testing. Bret Pettichord presents seven key steps: improve the testing process, define requirements, prove the concept, champion product testability, design for sustainability, plan for deployment, and face the challenges of success. Follow these steps as you staff, tool, or schedule your test automation project, and you will be well on your way to success!
|
Bret Pettichord, Tivoli Systems
|
|
Why Software Fails (And How Testers Can Exploit It) Testers know all too well that software fails. If we can understand the fundamental reasons why this happens, we can become more efficient and effective at finding bugs. James Whittaker explains the reasons why software fails and demonstrates how this knowledge can be used to break real software. The technology described has emerged from three years of contract testing at Florida Tech in which teams of students test (and break) post-release commercial software. Learn how to overrun buffers, cause memory violations, force incorrect results to be computed, and generally wreak havoc on your favorite software applications.
|
James Whittaker, Florida Institute of Technology
|
|
The Influential Test Manager Many of us have worked in test groups where we felt as if we didn't have enough time, staff, or computer resources to do the work. We may not even know precisely what we need to test. Consequently, we feel that while development may be in control, we certainly are not. Johanna Rothman contends that testers do not have to work this way. Learn effective ways to develop and use your influence within your organization to help your test group-and project-succeed. Discover how to discuss your perspective with your peers and managers and obtain buy-in on your test plans and objectives from the rest of the project team.
|
Johanna Rothman, Rothman Consulting Group, Inc.
|
|
Senior Management Asks: Will We Ever Finish Testing? Based on his testing experiences, Mike Lee illustrates through practical examples the steps taken to dramatically raise the probability of a successful test improvement implementation. Learn how major benefits were achieved in a complex environment with a very limited timeframe through changes in test strategy, administration support, agreement of ownership, and the establishment of basic metrics. Then, you too can answer senior management's question.
|
Mike Lee, CPT Consulting
|