Beginning Structured Software Testing

  Show the Value that Makes Developers, Users, and Managers Want to Test
2 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.


 

HOW TESTING CAN CUT EFFORT & TIME

  • Testing for correctness vs. testing for errors
  • V-model and objectives of each test level
  • Why developers, managers, users resist
  • Defect injection, detection, ejection metrics
  • Reactive testing—out of time, but not tests
  • Proactive Testing™ Life Cycle model
  • CAT-Scan Approach? to find more errors
  • Static and dynamic testing approaches
  • Developer vs. independent test group testing
  • Strategy—help find/prevent errors early
  • Test planning to save the developer’s time
  • Gaining value by applying concepts yourself
 

UNIT TESTING--FUNCTIONAL

  • Why exhaustive testing is impossible
  • Design to get most from time, resources
  • Functional (black box) testing strategy
  • 3-level top-down test planning and design
  • Functionality matrix, use case format
  • Equivalence classes and boundary values
  • Error guessing, heuristics, and risk analysis
  • Defining test cases, scripts and matrices
  • Test case specifications vs. test data values
 

TEST PLANNING VALUE NOT BUSYWORK

  • IEEE Standard for Test Documentation
  • Enabling manageability, reuse, selectivity
  • Entry and exit criteria, smoke tests
  • Master test planning risk-based strategy
  • Letting testing drive development
  • Preventing showstoppers and excess rework
 

UNIT TESTING--STRUCTURAL

  • Structural (white box) levels of coverage
  • Flowgraphing logic paths
  • Applying structural paths to functionality
 

INTEGRATION & SYSTEM TESTING

  • Graphical technique to simplify integrations
  • Moving integration error detection earlier
  • Daily, top- and bottom-down builds strategy
  • Iterative development testing issues
  • C/S, O-O, GUI, Web testing checklists
 

DEFECT REPORTING

  • Keys to effective testing
  • Defect isolation and reproducibility
  • Defect categorization
  • Projecting shipment date from defect trends
  • Measuring and evaluating test effectiveness Test metrics to save the developer’s time
 

ADDITIONAL TEST CONSIDERATIONS

  • Types of automated test tools
  • Key automation issues and tradeoffs
  • Formal reviews to catch more errors earlier
   
Seminars
Articles
Upcoming Events
About Go Pro
Contact Us