|
|
|
|
|
|
|
|
|
Elisabeth Hendrickson, Quality Tree Consulting
|
 |
When a development team adopts an agile process such as Scrum
or XP, testers find that their traditional practices no longer fit. The extensive
up-front test planning and heavyweight test documentation used in traditional development
environments just get in the way in an agile world. In this participative workshop,
you experience the transition to agile through a paper-based simulation (no programming
required). In a series of iterations, the team attempts to deliver a product that
the customer is willing to buy, thus generating revenue for the company. As with
real projects, producing a working product on a tight schedule can be challenging.
After each iteration, your team reflects on key events and adjusts to increase productivity
for the next iteration. Learn to apply the principles of visibility, feedback, communication,
and collaboration to increase the team’s rate of delivery. By the end of the
workshop, you will have a visceral understanding of agile and, in particular, the
shifting role of Test/QA in agile development.
|
|
Elisabeth Hendrickson began working
in the software industry in 1984. She has held positions as a Tester, Programmer,
Test Automation Manager, Quality Engineering Director, and Technical Writer working
for companies ranging from a 20-person startup to a large multi-national software
vendor. Elisabeth Hendrickson founded her company, Quality Tree Consulting, in 1997
to provide training and consulting in software quality and testing. Elisabeth is
frequently invited to speak at conferences around the world. In 2003, Elisabeth
became involved with the Agile community, became a Certified Scrum Master, and in
2006, she joined the board of directors of the Agile Alliance. Today, Elisabeth
splits her time between teaching, speaking, writing, and working on Extreme Programming
teams with test-infected programmers who value her obsession with testing.
|
|
|
|
|
|
|
|
|
|
All testers know that we can create
many more test cases than we will ever have time to create 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 and their associated coverage metrics.
Evaluate more informal approaches such as random and hunch-based testing and learn
about the importance of exploratory testing to enhance your testing ability. Choose
the right test case documentation format for your organization. Use the test execution
results to continually improve your test designs.
|
|
Lee Copeland has more than thirty-five
years of experience as a consultant, instructor, author, and information systems
professional. He has held a number of technical and managerial positions with commercial
and non-profit organizations in the areas of applications development, software
testing, and software development process improvement. Lee frequently speaks at
software conferences both in the United States and internationally and currently
serves as Program Chair for the Better Software Conference & Expo and the STAR
testing conferences, and SQE’s new Agile Development Practices conference.
Lee is the author of A Practitioner’s Guide to Software Test Design, a compendium
of the most effective methods of test case design. |
|
 |
|
|
|
|
|
|
|
|
Rick Craig, Software Quality Engineering
|
|
The key to successful testing is effective and timely planning.
Rick Craig introduces proven test planning methods and techniques, including the
Master Test Plan and level-specific test plans for acceptance, system, integration,
and unit testing. Rick explains how to customize an IEEE-829-style test plan and
test summary report to fit your organization’s needs. Learn how to manage
test activities, estimate test efforts, and achieve buy-in. Discover a practical
risk analysis technique to prioritize your testing and help you become more effective
with limited resources. Rick offers test measurement and reporting recommendations
for monitoring the testing process. Discover new methods and develop renewed energy
for taking test management to the next level in your organization.
|
|
A frequent
speaker at testing conferences, Rick Craig
is recognized worldwide as an expert test and evaluation instructor with Software
Quality Engineering. He has implemented and managed testing efforts on large-scale,
traditional, and embedded systems, and co-authored a study that benchmarked industry-wide
processes. Rick is co-author of the reference book Systematic Software Testing.
|
|
|
|
|
|
|
|
|
|
|
Paco Hope, Cigital |
|
Software security testing is a key element in your quality assurance
strategy for protecting your applications and critical data. Organizations need
applications that not only work correctly under normal use, but continue to work
acceptably in the face of a malicious attack. Software security testing, which extends
beyond basic functional requirements, is a critical part of secure software development.
By showing you how to use security risk information to improve your test strategy
and planning, Paco Hope helps you build confidence that attackers cannot turn security
risks into security failures. You’ll learn to think like an attacker and develop
test cases for security requirements. Explore a white-box approach that looks inside
your code to help you design your tests. By employing risk-based security testing,
you can achieve the most benefits with less effort and avoid downstream security
problems and mitigation costs. Paco offers an eye-opening experience for all QA
professionals responsible for test strategies, plans, and designs. It will change
the way you think about test development.
|
|
A Managing
Consultant at Cigital, Paco Hope has more
than twelve years of experience in software and operating system security. His areas
of expertise include software security policy, code analysis, host security, and
PKI. Paco has worked extensively with embedded systems in the gaming and mobile
communications industries, and has served as a subject matter expert on issues of
network security standards in the financial industry. Paco is co-author of Mastering
FreeBSD and OpenBSD Security. Prior to joining Cigital, he served as director of
product development for Tovaris, Inc. and head systems administrator in the Department
of Computer Science at the University of Virginia. |
|
|
|
|
|
|
|
|
|
|
Dale Perry, Software Quality Engineering
|
|
What does it take to properly plan and implement a performance
test? What factors need to be considered? What is your performance test tool telling
you? Do you really need a performance test? Is it worth the cost? These questions
plague all performance testers. In addition, many performance tests do not appear
to be worth the time it takes to run them, and the results never seem to resemble—yet
alone predict— production system behavior. Performance tests are some of the
most difficult tests to create and run, and most organizations don’t fully
appreciate the time and effort required to properly execute them. Dale Perry discusses
the key issues and realities of performance testing—what can and cannot be
done with a performance test, what is required to do a performance test, and what
the test “really” tells you.
|
|
A partner
of IT communication, Dale Perry has more
than 30 years experience in information technology. He has been a programmer/analyst,
database administrator, project manager, development manager, tester, and test manager.
Dale’s project experience includes large systems development and conversions,
distributed systems, on-line applications, both client/server and web based. He
has also been a professional instructor for over 15 years and has presented at numerous
industry conferences on development and testing. With Software Quality Engineering
for eleven years, Dale has specialized in training and consulting on testing, inspections
and reviews, and other testing and quality related topics.. |
|
|
|
|
|
|
|
|
|
|
Robert Sabourin, AmiBug.com, Inc. |
|
Turbulent Web development and other
market-driven projects experience almost daily requirements modifications, changes
to user interfaces, and the continual integration of new functions, features, and
technologies. Robert Sabourin shares proven, practical techniques to keep your testing
efforts on track while reacting to fast-paced projects with changing priorities,
technologies, and user needs. Rob covers test planning and organization techniques,
scheduling and tracking, blending scripted and exploratory testing, identifying
key project workflows, and using testing and test management tools. Learn how to
create key decision-making workflows for test prioritization and bug triage, adapt
testing focus as priorities change, identify technical risks, and respect business
importance. Come away with a new perspective on your testing challenges and discover
ways to take control of the situation—rather than to be controlled by it.
|
|
Robert Sabourin
has more than twenty-five years of management experience,
leading teams of software development professionals. A well respected member of
the software engineering community, Robert has managed, trained, mentored, and coached
hundreds of top professionals in the field. He frequently speaks at conferences
and writes on software engineering, SQA, testing, management, and internationalization.
The author of I am a Bug!, the popular software testing children’s book, Robert
is an adjunct professor of Software Engineering at McGill University. |
|
 |
|
|
|
|
|
|
|
|
Richard Bender, Bender RBT, Inc. |
|
Testers use requirements as an oracle to verify the success
or failure of their tests. Richard Bender presents the principles of the Requirements
Based Testing methodology in which the software's specifications drive the testing
process. Richard discusses proven techniques to ensure that requirements are accurate,
complete, unambiguous, and logically consistent. Requirements based testing provides
a process for first testing the integrity of the specifications. It then provides
the algorithms for designing an optimized set of tests sufficient to verify the
system from a black-box perspective. Find out how to design test cases to validate
that the design and code fully implement all functional requirements. Determine
which test design strategy—cause-effect graphing, equivalence class testing,
orthogonal pairs, and more—to apply to your applications. By employing a requirements
based testing approach, you will be able to quantify test completion criteria and
measure test status.
|
|
Richard Bender has been involved
in test and evaluation since 1969. He has authored and coauthored books and courses
on quality assurance and test, software development lifecycles, analysis and design,
software maintenance, and project management. He has worked with an international
clientele in a wide range of industries from financial to academic. |
|
|
|
|
|
|
|
|
|
|
Jon Bach, Quardev, Inc.
|
|
The agile nature of exploratory testing
makes it a widely-used and effective test approach, especially when testing time
is limited. But despite the ability of testers to rapidly apply their skill, exploratory
testing is often dismissed by project managers who regard exploration as unreproducible,
immeasurable, and unaccountable. If you find this to be true where you work, a solution
may be to use Session-Based Test Management (SBTM), developed by Jon Bach and his
brother James to solve these problems. In SBTM, testers are assigned areas of a
product to explore, and testing is time-boxed in “sessions” which have
mission statements called “charters”. Together, these create a meaningful
and countable unit of work. Using a simulated project, you’ll practice elements
of sessions, including chartering, paired testing (working with another tester on
the same mission), storytelling (taking notes during your testing) and debriefing
(responding to questions after your session). Jon will use a freely available, open
source tool to help manage and measure testing effort done in sessions.
|
|
Jon
Bach is senior consultant and Manager for Corporate
Intellect at Quardev, Inc., a Seattle outsource test lab where he manages testing
projects ranging from a few days to several months using Rapid Testing techniques.
In 2000, Jon and his brother James invented Session-Based Test Management for managing
and measuring exploratory testing. In his thirteen years of testing, Jon has been
a test contractor, full-time test manager, and consultant for companies such as
Microsoft and Hewlett-Packard. He has written articles for both Better
Software and Computer magazines. |
|
|
|
|
|
|
|
|
|
|
|
Organizations that develop software
always profess absolute commitment to product quality and customer satisfaction.
At the same time, they often believe that “all that testing isn’t really
necessary.” Test managers must be able to quantify the financial value of
testing and substantiate their claims with empirical data. Susan Herrick provides
experienced test managers with quantitative approaches to dispelling the prevailing
myths about the negative bottom-line impact of testing, to making a compelling business
case for testing throughout the project life cycle, and to providing decision-makers
with information that allows them to make fiscally responsible choices about test
efforts. During a hands-on activity, you will calculate, analyze, and substantiate
answers to such questions as, “What will it cost if we don’t test at
all?” “Should we rely on the system and acceptance testers to find all
the defects?” “Can our experienced developers test their own code?”
and “Should experienced users perform the acceptance testing?” Answer
these and more questions with the numbers at hand to back up your claims.
Laptop
Required |
|
To benefit fully from the hands-on activity, each participant
should bring a laptop. All participants will receive a CD containing a calculation
tool (with full instructions) as a takeaway. |
|
|
With twenty-five years of involvement in the development
of IT solutions and fifteen years of testing experience,
Susan Herrick is currently a Testing Architect and
corporate leader of Testing Management and Consulting for the Global Testing Capability
at EDS. She provides expertise, leadership, and guidance in “architecting
testing solutions,” particularly in the areas of testing strategy development
and testing management/measurement. Susan has contributed to the development of
supporting processes, tools, and techniques in these key areas. |
|
 |
|
|
|
|
|
|
|
|
Martin Pol, POLTEQ IT Services BV
|
 |
When outsourcing all or part of your testing efforts to a third-party
vendor, you need a special approach to make testing effective and controlled. Martin
Pol explains the roadmap to successful outsourcing, how to define the objectives
and strategy, and what tasks should be outsourced and what tasks should not—at
least not yet. He describes how to select your supplier and how to migrate, implement,
and cope with organizational issues. Martin discusses contracts, service level agreements,
compensation issues, and monitoring and controlling the outsourced test work, including
specific metrics. The good news for testers is that outsourcing requires more testing—not
less—and that new testing jobs are coming into existence. Testing the outsourcing
is becoming a very popular control mechanism for outsourcing in general.
|
|
Martin Pol has played a significant
role in helping to raise the awareness and improve the performance of testing worldwide.
Martin provides international testing consulting services through POLTEQ IT Services
BV. During recent years he has specialized in test outsourcing/offshoring and he
has developed an approach to successfully deal with this phenomenon. His experiences
in both India and China are of great value. He has supported many organizations
to define the test service levels, to organize the prerequisites and to implement
test outsourcing management and monitoring.
|
|
|
|
|
|
|
|
|
| | |
