|
|
 |
|
|
|
|
|
|
STARWEST 2009 Tutorials
|
|
| |
|
| Lee Copeland, Software Quality Engineering |
 |
All testers know that we can create many more test cases than we will ever have time to design and execute. The major problem in testing is choosing a small, “smart” subset from the almost infinite number of possibilities available. Join Lee Copeland to discover how to design test cases using formal black-box techniques, including equivalence class and boundary value testing, decision tables, state-transition diagrams, and all-pairs testing. Also, explore white-box techniques with their associated coverage metrics. Evaluate more informal approaches, such as random and hunch-based testing, and learn the importance of using exploratory testing to enhance your testing ability. Choose the right test case design approaches for your projects. Use the test results to evaluate the quality of your products and the quality of your test designs.
|
|
| Learn more about Lee Copeland |
|
|
|
|
| |
| |
| Adopting an agile development methodology changes many familiar practices for both developers and testers. Join Amir Kolsky to examine the challenges many testers face as agile development practices move into the mainstream and into their organizations. Teams new to agile or exploring agile practices have discovered that the transition from traditional testing practices to the lean-agile “test first” approach is a significant challenge for the development team and, in particular, for test engineers. Learn how requirements practices and documents differ when the team is using agile development practices. Find out about new workflows needed for test development and execution and process changes for tracking and repairing defects. Discover how faster release schedules can affect testing and the entire team. Using case studies—both successes and failures—Amir discusses transition strategies and solutions for test and development teams. Learn from these experiences and apply their lessons to the challenges you may face as you enter the land of agile development. |
|
| Learn more about Amir Kolsky |
|
|
|
|
| |
| |
| Martin Pol and Ruud Teunissen, POLTEQ IT Services BV |
|
What is the maturity of your testing process? How do you compare to other organizations and to industry standards? To find out, join Martin Pol and Ruud Teunissen for an introduction to the Test Process Improvement (TPI®) model, an industry standard for testing maturity assessments. Although many organizations want to improve testing, they lack the foundation required for success. Improving your testing requires three things: (1) understanding key test process areas, (2) knowing your current position in each of these areas, and (3) having the tools and skills to implement needed improvements. Rather than guessing what to do, begin with the TPI® model as your guide. Using examples of real world TPI® assessments that they have performed, Martin and Ruud describe a practical assessment approach that is suitable for both smaller, informal organizations and larger, formal companies. Take back valuable references, templates, examples, and Web links to start your improvement program.
TPI® is a registered trademark of Sogeti USA LLC. |
  |
Learn more about Martin Pol
Learn more about Ruud Teunissen |
|
|
|
|
| |
| |
| Randy Rice, Rice Consulting Services, Inc. |
|
Have you been thrust into the role of test team leader or are you in this role now and want to hone your leadership skills? Test team leadership has many unique challenges, and many test team leaders—especially new ones—find themselves ill-equipped to deal with the problems they face. The test team leader must motivate and support the team while keeping testing on track within time and budget constraints. Randy Rice focuses on how you can grow as a leader, influence your team and those around you, and positively impact those outside your team. Learn how to become a person of influence, deal with interpersonal issues, and help your team build their skills and value to the team and the organization. Discover how to communicate your team’s value to management, how to stand firm when asked to compromise principles, and how to learn from your successes and failures. Develop your own action plan to become an influential test team leader. |
 |
| Learn more about Randy Rice |
|
|
|
|
|
|
| |
|
Testing generates a huge amount of raw data, which must be analyzed, processed, summarized, and presented to management so that effective decisions can be made quickly. As a test manager or tester, how can you present information about your test results so that decision-makers receive the correct message? Using his experiences as a test manager and consultant, Lloyd Roden shares ways to communicate with and disseminate information to management. Develop your skills so you become a “trusted advisor” to senior management rather than the classic “bearer of bad news.” Discover innovative ways to keep the information flowing to and from management and avoid losing control of the test process, particularly near the delivery date. Learn how to deal effectively with various controversies that often prevent senior managers from taking you seriously.
|
 |
| Learn more about Lloyd Roden |
|
|
|
|
| |
| |
|
| Julie Gardiner, Grove Consultants |
 |
Classification trees are a structured, visual approach used to identify and categorize variables within test objects, enabling testers to build effective and efficient test cases quickly. Julie Gardiner describes the fundamentals of classification trees and how they can be applied in both traditional and agile test environments. Using real-world examples, Julie shows you how to employ the classification tree technique, identifies the benefits and rewards of this technique, explains how it complements other testing approaches, and reveals its value at every stage of testing. She demonstrates a classification tree editor available to aid in building, maintaining, and graphically displaying classification trees. Take back a powerful new approach for overcoming the constant struggle we have when maintaining and assessing the impact of changing requirements on our test suites.
Laptop Required |
To take full advantage of this session, participants need to bring a laptop computer for this session. |
|
 |
| Learn more about Julie Gardiner |
|
|
|
|
| |
| |
Exploratory testing is an approach to testing that emphasizes the freedom and responsibility of the tester to continually optimize the value of his work. It is the process of three mutually supportive activities performed in parallel—learning, test design, and test execution. With skill and practice, exploratory testers typically uncover considerably more problems than when the same amount of effort is spent on scripted testing. All testers conduct exploratory testing in one way or another, but few know how to do it systematically to obtain the greatest benefits. Even fewer testers can articulate the process. Jonathan Kohl describes specific heuristics and techniques of exploratory testing to help you get the most from this highly productive approach. Jonathan focuses on the skills and dynamics of exploratory testing itself and how it can be combined with scripted approaches.
Laptop Required |
Laptop Required. This is a hands-on course. A laptop—preferably with Microsoft Windows capability—is required for some of the exercises. |
|
 |
| Learn more about Jonathan Kohl |
|
|
|
|
| |
| |
| Lisa Crispin, Ultimate Software |
|
Agile teams must deliver production-ready software every four-, two- or one-week iteration – or possibly every day! This goal can't be achieved without automated tests. However, many teams just can't seem to get traction on test automation. The challenge of automating all regression tests strikes fear into the hearts of many testers. How do we succeed when we have to release so often? By combining a collaborative team approach with an appropriate mix of tools designed for agile teams, you can, over time, automate your regression tests, and continue to automate new tests during each programming iteration. Lisa Crispin describes what tests should be automated, some common barriers to test automation, and ways to overcome those barriers. Learn how to create data for tests, evaluate automated test tools, implement test automation, and evaluate your automation efforts. An agile approach to test automation even helps if you’re a tester on a more traditional project without the support of programmers on your team. |
|
| Learn more about Lisa Crispin |
|
|
|
|
|
|
| |
| Harry Robinson, Microsoft |
 |
Harry Robinson’s mantra is “People should think—machines should test.” To achieve high-quality software while maintaining their sanity, smart testers get their test machines to do much of the “heavy lifting” of creating and executing tests. Model-based testing automatically generates tests from a description of an application's desired behavior—a model. Microsoft has shown that model-based tests are more cost-effective and dynamic than traditional scripted automation. Employing model-based testing requires using testers with greater test design skills, re-thinking how to measure the test team's contribution, and deciding where testing fits into the development process. Harry introduces state machines, test sequence generators, combinatorics, and heuristic oracles that will improve your testing skills and your software's quality. Learn how to use free tools, such as NModel, ModelJUnit, C#, WatiN, and PICT to generate and execute millions of tests for GUIs, APIs, and Web applications.
|
 |
| Learn more about Harry Robinson |
|
|
|
|
| |
| |
| Julie Gardiner, Grove Consultants |
|
Risks are endemic in every phase of every project. One key to project success is to identify, understand, and manage these risks effectively. However, risk management is not the sole domain of the project manager, particularly with regard to product quality. It is here that the effective tester can significantly influence the project outcome. Julie Gardiner explains how risk-based testing can shape the quality of the delivered product in spite of such time constraints. Join Julie as she reveals how you can apply product risk management to a variety of organizational, technological, project, and skills challenges. Through interactive exercises, you will get practical advice on how to apply risk management techniques throughout the testing lifecycle—from planning through execution and reporting. Take back a practical process and the tools you need to apply risk analysis to testing in your organization. |
|
| Learn more about Julie Gardiner |
|
|
|
|
| |
| |
| Janet Gregory, DragonFire, Inc. |
|
Traditional test plans are incompatible with agile software development because we don't know all the details about all the requirements up front. However, in an agile software release, you still must decide what types of testing activities will be required, and when you need to schedule them. Janet Gregory explains how to use the Agile Testing Quadrants, a model identifying the different purposes of testing, to help your team understand your testing needs as you plan the next release. Learn how to decide who does what testing—and when. Janet introduces you to alternative lightweight test planning tools that allow you to plan and communicate your big picture testing needs and risks. She describes what types of testing to consider when planning an agile release, the infrastructure and environments needed for testing, what goes into an agile “test plan”, how to plan for acquiring test data, and lightweight approaches to documenting your tests and recording test results.
|
 |
| Learn more about Janet Gregory |
|
|
|
|
| |
| |
| Rick Craig, Software Quality Engineering |
|
To be most effective, test managers must develop and use metrics to help direct the testing effort and make informed recommendations about the software’s release readiness and associated risks. Because one important testing activity is to “measure” the quality of the software, test managers must measure the results of both the development and testing processes. Collecting, analyzing, and using metrics is complicated because many developers and testers are concerned that the metrics will be used against them. Join Rick Craig as he addresses common metrics—measures of product quality, defect removal efficiency, defect density, defect arrival rate, and testing status. You will learn the guidelines for developing a test measurement program, rules of thumb for collecting data, and ways to avoid “metrics dysfunction.” Rick also identifies various metrics paradigms, including Goal-Question-Metric, and discusses the pros and cons of each. Participants are urged to bring their metrics problems and issues for use as discussion points.
|
 |
| Learn more about Rick Craig |
|
|
|
|
|
| |
Top of Page
|
|
|
|
|
|
 |
Software Quality Engineering • 330 Corporate Way, Suite 300 • Orange Park, FL 32073
Phone: 904.278.0524 • Toll-free: 888.268.8770 • Fax: 904.278.4380 • Email: sqeinfo@sqe.com
© 2009 Software Quality Engineering, All rights reserved. | | | |
