Show the Value that Makes Developers, Users, and Managers
Want to Test 3 Day Intensive Seminar Workshop
This interactive workshop is aimed at
turning testing into a valuable activity that actually helps you
get your work done quicker—as well as better. Simple but
powerful structured techniques are presented to break testing
into manageable pieces and perform a series of risk analyses so
limited time can be devoted to performing the most important testing
earlier and more thoroughly. Participants apply checklists and
guidelines to design test cases and discover numerous conditions
they ordinarily would have overlooked. By understanding why and
how things work, they can be adapted more easily to one’s
own situation. Exercises enhance learning by allowing participants
to practice applying techniques to an actual case.
Participants will learn:
* A structured Proactive Testing™ model of testing
that should be performed throughout the life cycle.
* Ways testing actually can cut time, effort, and aggravation
for users, developers, and managers.
* Writing industry-accepted test plans and test designs
that make testing easier and more reliable.
* Multiple techniques/checklists to design more thorough
tests and discover overlooked conditions.
* Applying risk analysis and reusable testware to perform
more of the important testing in less time.
WHO SHOULD ATTEND: This course
has been designed for testers, developers, analysts, designers,
auditors, users, and managers who plan, oversee, and/or carry out
testing of software products.
TURNING AROUND TESTING’S IMAGE
Objectives, types, and scope of testing
Injection, detection, ejection economics
Defect measures and testing effectiveness
Why developers, managers, users resist
Reactive testing—out of time, but not tests
Proactive Testing™ Life Cycle model
Test planning to save the developer’s time
Caution: “Emperor’s New Clothes” risk
CONCEPTS OF TESTING
Testing for correctness vs. testing for errors
Keys to effective testing
Static and dynamic testing approaches
Developer vs. independent test group testing
Defect categorization, configuration control
Projecting shipment date from defect trends
CAT-Scan Approach? to find more errors
When testing is “good enough” to stop
Measuring and evaluating test effectiveness Test metrics to save the developer’s time