|
|
|
STAREAST 2006 Concurrent Sessions
Go To: Agile Methods | Exploratory Testing | Outsourced Testing | Performance Testing | Security Testing |
Special Topics | Test Automation | Test Management | Test Metrics | Test Techniques
View by Date
| Exploratory Testing | | | T13 is a Double-Track Session! | | Thursday, May 18, 2006 1:30 PM |
Testing Outside the Bachs
James Bach, Satisfice Inc
Jon Bach, Quardev Laboratories
Simply put, exploratory testing means designing your tests as you perform them. When it’s done well, it’s a fantastically productive and rewarding approach to testing. However, to do it well requires training, practice, and discipline. Lecture presentations about exploratory testing are a poor substitute for seeing it and doing it. So . . . plan to bring your laptop to this session and test along with James Bach and Jon Bach as they demonstrate exploratory testing in a live testing workshop. Participate or just observe as exploratory testing is performed in real time with play-by-play and color commentary. Learn how to bring structure to this apparently unstructured testing method. See if you can find bugs that they do not find as you test “outside the Bachs”!
If you plan to bring your laptop and join in this live testing workshop, make sure it is charged up. Email james@satisfice.com for directions on downloading the software onto your computer. |
| | | Friday, May 19, 2006 10:00 AM |
The Art of Exploration
David Gilbert, Sirius Software Quality Associates, Inc.
In order for exploratory testing to be perceived as a valuable process by all stakeholders in the organization, we need to make sure the result of that testing—our documentation—is presented with the same professionalism and attention to detail that distinguishes an artistic masterpiece from a paint-by-number kit. David Gilbert discusses the practical steps testers can take to improve the perceived value of exploratory testing in their organizations. He explains how we can apply a consistent, professional, and structured methodology to our exploratory testing and employ processes that will consistently create the level of detailed output that is considered the hallmark of any investigative analysis. Finally, David tells us how better to communicate the value of exploratory tests and document both the process and results of exploration in a way that stakeholders will understand.
• Why stakeholders may question the value of exploratory testing
• Steps during testing and analysis afterward to increase the benefits of exploration
• Changes in the presentation of exploratory results to improve its perceived value |
| | | Friday, May 19, 2006 11:15 AM |
Session-Based Exploratory Testing: A Large Project Adventure
George Bliss, Captaris
You know the story: Marketing wants more features, faster release cycles, and release dates that do not slip. Customers want new functions and software that does not break. Testers and developers want to release high quality software with limited resources. Management wants good information to make ship don’t ship decisions. What if, facing all of these wants, you could reduce testing time by up to 50% and release better code as evidenced by fewer defects with lower severity after release? George Bliss shows you how a switch from traditional script-based testing to session-based exploratory testing—along with agile development practices and more automation—achieved those results. With session-based exploratory testing, they delivered real-time status updates to management and helped to make the quality of software everyone’s business.
• Improved communication and reporting to stakeholders with session-based exploratory testing
• Spread the decision surrounding release decisions to all critical groups
• Tools for handling the results from session-based exploratory testing |
| |
|
|
