|
|
|
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
| Test Techniques | | | Wednesday, May 17, 2006 11:30 AM |
Capitalize on Static Analysis Testing
James Bach, Satisfice Inc
By evaluating software based on its form, structure, content, and documentation, you can use static analysis to test code within a program without actually running or executing the program. Static analysis testing helps us stop defects from entering the code stream in the first place rather than waiting for the costly and time-consuming manual intervention of testing to find defects. With real-world examples, Djenana Campara describes the mechanics of static analysis—when it should be used, where it can be executed most beneficially within your testing process, and how it works in different development scenarios. Find out how you can begin using code analysis to improve code security and reliability.
• The mechanics of automated static analysis
• Static analysis for security and reliability testing
• Integrating static analysis into the testing process |
| | | W7 is a Double-Track Session! | | Wednesday, May 17, 2006 1:45 PM |
Testing Dialogues—Technical Issues
Esther Derby, Esther Derby Associates Inc
Johanna Rothman, Rothman Consulting Group, Inc.
Is there an important technical test issue bothering you? Or, as a test engineer, are you looking for some career advice? If so, join experienced facilitators Esther Derby and Johanna Rothman for “Testing Dialogues—Technical Issues.” Practice the power of group problem solving and develop novel approaches to solving your big problem. This double-track session takes on technical issues, such as automation challenges, model-based testing, testing immature technologies, open source test tools, testing Web services, and career development. You name it! Share your expertise and experiences, learn from the challenges and successes of others, and generate new topics in real-time. Discussions are structured in a framework so that participants receive a summary of their work product after the conference. |
| | | Thursday, May 18, 2006 9:45 AM |
Branch Out Using Classification Trees for Test Case Design
Julie Gardiner, QST Consultants Ltd.
Classification trees are a structured, visual approach to identify and categorize equivalence partitions for test objects to document test requirements so that anyone can understand them and quickly build test cases. Join Julie Gardiner to look at the fundamentals of classification trees and how they can be applied in both traditional and agile test and development environments. Using examples, Julie shows you how to use the classification tree technique, how it complements other testing techniques, and its value at every stage of testing. She demonstrates a classification tree editor that is one of the free and commercial tools now available to aid in building, maintaining, and displaying classification trees.
• How to develop classification trees for test objects
• The benefits and rewards of using classification trees
• When and when not to use classification trees |
| | | Thursday, May 18, 2006 11:15 AM |
Put on a Gamer’s Hat with Data Flow Testing
Mitch Goldman, Mitch Goldman (Self)
Designing tests from the point-of-view of the data is like playing a first-person-shooter game. It’s fun—and it can give you a deeper understanding of the application under test. Data moves through an application like a player traverses a game. It flows through a maze (to and from the database), encounters enemies (validations), picks up inventory items (attributes), and solves puzzles (business rules) to win (accepted) or lose (rejected). Designing tests from the data’s point of view is a useful heuristic to help pinpoint the origin of the bug and to reveal bugs that may otherwise go undetected. Mitch Goldman employs the game analogy to illustrate ways to break down an application into its data-flows, design the tests, and execute them. So, put your gamer hat on and start designing tests from the data’s point of view. Have a “death match” with your bugs!
• How to break down an application into its data-flows
• Design and execute the data-flow tests to find new bugs
• Tools for designing and executing data-flow tests |
| | | Thursday, May 18, 2006 1:30 PM |
Code Coverage: Where Does It Fit?
Dale Brenneman, McCabe Software
Many organizations use code coverage almost religiously in their testing. Just as many or more organizations do not use code coverage or have tried it and stopped. If you want to begin using code coverage for the first time or improve its value and usage within your team, come hear what Dale Brenneman has to share. Using real-life examples, Dale explains the value of code coverage analysis as part of a comprehensive test plan and the potential side effects when you do not use code coverage. Find out about the many levels of code coverage and ways to enhance the value of code coverage analysis with other analysis techniques. Take away a step-by-step approach for integrating code coverage analysis into your organization's test process and fitting it into your functional test automation program.
• The levels of module code coverage: entry, line, statement, branch, Boolean, cyclomatic path, all paths
• The levels of application coverage: sums of module, module entry, integration calls, integration paths, all paths
• A sample of the results and reports from code coverage analysis |
| | | Thursday, May 18, 2006 3:00 PM |
Q-Patterns for Reusable Test Cases
Vipul Kocher, PureTesting
You can think of Q-Patterns as a structured set of questions (tests) about the different aspects of a software application under test. They are questions about the system that are categorized, grouped, sorted, and saved for reuse. These Q-Pattern questions can be written ahead of time and stored in a repository of test case templates, developed for requirements and design reviews or built in real-time as a way to both guide and document exploratory testing sessions. See examples of Q-Patterns that Vipul Kocher has developed for error messages, combo boxes, login screens, and list handling. Learn how to associate related Q-Patterns and aggregate them into hierarchical and Web models. Take back the beginnings of Q-Patterns for your test team and organization.
• Sharable and reusable test case designs
• Templates to organize requirements and design reviews
• A tool for capturing exploratory testing experiences |
| | | Friday, May 19, 2006 10:00 AM |
You'll Be Surprised by the Things Testers Miss
James Lyndsay, Workroom Productions
Why do some bugs lie undetected until live operation of the software and then almost immediately bite us? Drawing on instances of problems that were obvious in production—but missed or nearly missed in testing, James Lyndsay can help you catch more bugs starting the day you return to work. James first describes bugs not found because too little time is spent on testing. Then, looking at the testers’ knowledge, he discusses bugs missed because of requirements issues or because testers did not understand the underlying technology’s potential for failure. In the most substantial part of the session, James looks at bugs missed because they could not be observed or because testers skimmed over the issue. Learn to recognize each type of testing problem and discover ways to mitigate or eliminate it.
• Coding errors that are hard to spot with typical test design techniques
• Working with emergent behaviors and unexpected risks
• What to do with bugs that should have been found earlier |
| | | Friday, May 19, 2006 11:15 AM |
All I Need to Know about Testing I Learned from Dr. Seuss
Robert Sabourin, AmiBug.com Inc
Through the stories and parables of Theodor Geisel, we can learn simple, yet remarkably powerful approaches for solving testing problems. In a tour of common issues we encounter in testing—test planning, staff training, communications, test case design, test execution, status reporting, and more, Robert Sabourin explains how you can apply lessons from the great books of Dr. Seuss to testing. Green Eggs and Ham teaches us combinations; Go, Dog, Go teaches us the value of persistence; Because a Little Bug Went Kachoo teaches us about side effects, chaos, and risk management. Others such as Hop on Pop, Marvin K Mooney, I Can Read with My Eyes Shut, and Inside Outside UpSide Down all have important lessons about how to get things done on software projects. Learn some simple truths and take away some heuristic testing aids to become a more productive and effective tester.
• Important heuristics to better test planning
• Different testing approaches that can be used for the same problem
• A back to basics way to improve performance |
| |
|
|
