|
|
 |
Concurrent Sessions
WEDNESDAY, MAY 15
|
|
Topical Tracks–Real World Experiences
The STAREAST conference program is designed to serve the needs of software testing and quality engineering managers and professionals. At STAR, you’ll learn about the latest strategies, ideas, and techniques being used by leading software organizations. STAR’s unique, real-world approach provides you with the knowledge and practical skills you need to ultimately build and deliver better software.
|
| WEDNESDAY, MAY 15, 1:00 PM Go to 2:15 PM Go to 3:15 PM | W1 Test Management
The W-Model: Strengthening the Bond Between Development and Test
Andreas Spillner, Hochschuele Bremenn
In software development, 30 to 40% of all software activities are testing-related. That’s why it’s critical to launch test activities at the beginning of the project rather than after the coding is completed. While new software development models such as the Rational Unified Process and eXtreme Programming continue to be popular with practitioners, the V-model has gained particularly wide acceptance. Based on the V-model, this session demonstrates how the tasks for testing relate to the tasks in the development model. This new testing model — the W-model — further clarifies the priority of the tasks and the dependence between the development and testing activities. Though as simple as the V-model, the W-model clarifies the importance of testing and the ordering of the individual testing activities.
• See how the W-model of testing parallels development’s V-model
• Illuminate the dependencies between test and development activities and make them work to your advantage
• Learn why testing and debugging are not the same thing |
| W2 Test Techniques
Testing Your Software’s Requirements
Brian Lawrence, Coyote Valley Software
Many testing organizations focus primarily on software executable code, but that’s not the only thing you can test. For instance, did you ever consider testing your software requirements? When you test only code, you face some big disadvantages, not to mention that design defects often aren’t even fixable because they demand too much effort, too late in the release cycle. In fact, it's difficult to even report some requirements defects since the developers have already committed to the design strategy. But if you test your requirements early in the game, you can discover defects before they’re cast into designs and code, consequently saving your organization potentially huge rework costs.
• See requirements testing demonstrated in an interactive session
• Learn to avoid going down a poorly chosen development path by testing requirements
• Find out how to organize requirements effectively |
| W3 Test Automation
Unified Test Automation Using XML
Rodrigo Geve, Geve & Associates, Inc.
Are you looking to reduce the maintenance costs of your testware? Unified Test Automation (UTA) is one approach that’s demonstrated cost-saving success. UTA serves as a cost-reduction strategy by centralizing test resources and minimizing the overhead of maintaining the different components of testware, such as test documents, test software, and test data. The advent of new technologies such as the XML markup language and associated XML third-party tools for editing XML content has produced an ideal framework for the centralization of all testware. Rodrigo Geve cites specific examples and explains how this has been achieved.
• Get a well-rounded introduction to the UTA method
• Use the “data-driven testing” approach within the context of XML
• Explore a test automation framework built on the UTA concepts |
| W4 Professional Development
Movin’ on Up: Making the Transition to Test Lead or Manager
Johanna Rothman, Rothman Consulting Group, Inc.
Want to be a test lead? Ready to take on the responsibilities of test management? Making the transition to a lead, then a management position, takes more than just guts — it takes preparation. This presentation illuminates some the technical aspects you’ll encounter when transitioning to test lead or test manager, including: organizing and managing the testing; working with the project manager and the rest of the project team; and deciding how, when, and what to invest in your test infrastructure. You’ll also explore some of the nontechnical aspects such as coaching and mentoring, giving feedback, and providing work direction.
• Get tips on how to move from technical work to management work
• Determine how to organize the work other people do so they can be effective managers
• Figure out how to navigate changed relationships |
| W5 Advanced Topics
Testing in the .NET Maze
Thomas Arnold, Xtend Development, Inc.
.NET is a multi-tiered approach to developing applications for Windows OS and Web applications. While these are new development tools, many testing requirements remain the same, yet require additional emphasis by a QA organization. Plus, with .NET’s extra layers of abstraction, even more developers enter the programming arena with fewer technical skills than previously needed for standard Windows development. For instance, if a bug is found “in the depths” there’s now more likely to be a work-around to the issue instead of a true fix. In other words, treating the symptoms instead of finding a cure will now become the norm. This presentation introduces you to the big picture of .NET and what you need to be aware of as your employer moves in this new direction.
• Obtain an introduction to .NET
• Discover why black box testing may not be enough
• Find out what the future holds as .NET is inevitably embraced |
| | WEDNESDAY, MAY 15, 2:15 PM Go to 1:00 PM Go to 3:15 PM | W6 Test Management
Four Keys to Better Test Management
Christopher P. DeNardis, Rockwell Automation
Three years ago, Christopher DeNardis embarked on a career as a software tester. After just one year of testing, he was promoted to leader of the test group. In this session, he shows you the four keys to getting through those times and becoming better organized as a test manager: 1. a common set of ground rules on the test progress, defect reporting, and verification; 2. the ability to convey how your team’s testing is going on a frequent basis; 3. knowing what needs to be tested and being able to stand behind the reasons why; and 4. maintaining good communication with the development leaders to help move the product through the development phases.
• How to set up test guidelines or a charter for the group, then communicate and report results
• Learn to be proactive (rather than reactive) as a manager
• Get relevant tips whether you’re a new or seasoned test manager |
| | Double Track Session! (This track fills two time blocks.) | W7 Test Techniques
How to Break Software
James A. Whittaker, Florida Institute of Technology
Tr ying to figure out how you can become a more effective tester? That’s easy: Become a better bug hunter. This double-track presentation uncovers the root cause of software failure and offers techniques you can use to find bugs. James Whittaker shows you examples of real bugs and diagnoses their cause, while giving you the opportunity to ask questions based on your own determinations. He also describes a set of testing techniques designed to help find bugs in your applications more quickly. You’ll even walk away with some fun exercises to help create a better overall testing culture at your company.
• Explore the main reasons software fails
• How to expose system interfaces to testing scrutiny
• Get specific, prescriptive strategies that expose bugs in software |
| W8 Test Measurement
Blind Alleys in Automated Testing
Douglas Hoffman, Software Quality Methods, LLC
More often than not, even modest software test automation efforts fail to achieve their goals. Usually these project shortcomings happen because the introduction of test automation reduces the effectiveness of the test group, thereby reducing the number of tests and the number and complexity of product defects found. Several common misconceptions about the value and techniques for software test automation contribute to this problem. Douglas Hoffman explores some of the more common issues and addresses how to recognize and avoid them. He delves into each blind alley, describing each one and showing you how and why they sometimes lead to failure. He then offers you strategies for understanding and avoiding them.
• Walk through a baker’s dozen of “blind alleys”
• Determine which technical issues need to be addressed for automated testing
• Find new ways to explain the issues to management |
| | Double Track Session! (This track fills two time blocks.) | W9 Professional Development
Career Path Activities for Test Professionals
Eric Patel, RapidSQA
Ever wonder how some people seem to find the time to always do that “little extra” to benefit their careers? Have you ever thought about writing an article, speaking at a conference, or even teaching a course, but didn’t know where to begin? There are lots of ways to jump-start your career through professional development activities that benefit both you and your employer. Learn how your participation in these activities can enhance your career and market your company. Journey with the instructor and find the inspiration (and energy) to maintain a diversity of activities that’ll make your professional mark. Find out how easy it is to get started and where to obtain more information about updating your skills, sharing your knowledge, and helping others within our profession.
• The pros and cons of several professional development activities
• Discover the satisfaction, recognition, and fun you’ll enjoy as you lead by example
• Develop your personal action plan |
| W10 Advanced Topics
Applying Testing Expertise to the Retrospective Goldmine
Nick Borelli, Microsoft
Digging up postmortem project data is like mining for gold. The returns can be significant and long-term because this is where your best (and worst) practices really shine. By allowing your test groups to drive the retrospective activities, improvements can finally be built into the product lifecycle model instead of rotting in a postmortem report. By improving retrospective facilitation and follow-up, you’ll ultimately improve your software lifecycle process. Nick Borelli delivers a practical and proven approach to the retrospective process, and shows you how to build consensus for process improvements uncovered during retrospective analysis.
• Learn to conduct fruitful, moderated, and self-administered retrospectives
• Find ways to effectively roll out the retrospective data
• How to ensure follow-up on retrospective action items |
| | WEDNESDAY, MAY 15, 3:15 PM Go to 1:00 PM Go to 2:15 PM | W11 Test Management
Outsourcing Trials and Traps
Steve Jeffery, Powerquest
Sometimes outsourcing can help your business, but there’s too much at stake to take outsourcing lightly. This presentation teaches you the importance of identifying your critical needs before you even begin the task of selecting an outsourcing partner, because the risks are far too great for you to try to fix a major problem with chewing gum and bailing wire. You’ll also get practical guidelines for deciding what you need, finding the right partner, making it work your way and on your schedule, and deciding if it was worth it once you’re done. You’ll avoid outsourcing disasters by learning from the expensive lessons of others.
• Define your criteria for going outside the company
• Identify the requirements used to select the partner, not just the job
• Manage your partner better than you manage yourself |
| W12 Test Automation
Beyond Record and Playback: A Behind-the-Scenes View of Web Test Automation
Michael Prisby, United Parcel Service
Web-based test automation goes well beyond the mere action of recording manual test scripts and replaying them. Test automation is more of a development process than the normal quality assurance or test effort. This presentation takes an in-depth look into what it takes to truly automate Web site testing. You’ll explore the following building blocks: planning/analysis, design/development, implementation, and support.
• Get tips on making educated choices in the purchase of automated testing assets
• How to determine your test team’s ability in the manipulation of the test tool
• Find out why automation is not automatic |
| W13 Advanced Topics
Looking Ahead: Testing Tools in 2010
Sam Guckenheimer, Rational Software Corporation
It’s May 15, 2010, and you’re in a triage meeting reviewing the testing status and bugs in your telemedical software. The system uses real-time voice, video, graphics, and an expert knowledge base to support expert medical procedures in remote locations. As the test manager, you’re using trace diagrams, deployment diagrams, runtime fault injection, coverage views, test patterns, built-in self test, and other modern, agile techniques to review the bugs, diagnose faults, assign priorities, and update your test plans. Sam Guckenheimer contrasts the methods available to you in 2010 versus the techniques you used years ago when you were starting out as a test manager.
• Explore how software testing will evolve radically over the next decade, just as hardware testing did in the 1980s
• Review how test-first design and design for testability make a difference
• Uncover how patterns enable knowledge capture and test reuse |
| |
|
|
|
