Winning Approaches to Structured Software Testing

Win Testing Advocates by Helping Deliver Projects Faster, Cheaper, and Better
2-Day Intensive Seminar Workshop

Proactive Testing™ enables you to do more effective testing in less time, while also providing the value that overcomes traditional user, manager, and developer resistance to testing. By continually refocusing on the highest risks, and applying special techniques that spot many ordinarily-overlooked risks, Proactive Testing™ makes sure the most important testing is done in available time. Moreover, by catching more defects earlier when they are easier to fix, and actually preventing many showstoppers and other errors, Proactive Testing™ also can cut developers’ time, effort, and aggravation. This interactive workshop shows powerful proven Proactive structured test planning and design techniques that produce value, not busywork, and enable productive use of automated test tools. To enhance learning, participants practice each key technique in a series of exercises with various aspects of a real case fact situation.

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.

* Guidelines for using appropriate automated tools to enhance overall testing effectiveness.

* 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 testing professionals and others who manage and perform testing of software products, and also for analysts, designers, and system/project managers who need to know how Proactive Testing™ can cut software development time and effort.

HOW TESTING CAN CUT EFFORT & TIME

Testing for correctness vs. testing for errors
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
V-model and objectives of each test level
Dynamic, passive and active static testing
Developer vs. independent test group testing
Strategy—create fewer errors, catch more
Test activities that save the developer’s time

TEST DESIGN: BOTH VERB AND NOUN

Exercise: Disciplined brainstorming
Checklists find more overlooked conditions
Data formats, data and process models
Business rules, decision tables and trees
Equivalence classes and boundary values
Error guessing, condition combinations
Defect isolation, reproducibility,
Formal, informal Test Design Specifications
Exercise: Defining reusable test designs
Test Case Specifications vs. test data values
Exercise: Writing test cases, script/matrix

TEST PLANNING, VALUE NOT BUSYWORK

Risk elements, relation to testing
Proactive vs. reactive risk analysis
IEEE Standard for Test Documentation
Enabling manageability, reuse, selectivity
Master Test Plan counterpart to project plan
Approach, use of automated tools
Entry/exit criteria, anticipating change
Exercise: Anticipating showstoppers
Risk-based way to define test units
Letting testing drive development
Preventing major cause of overruns

AUTOMATED TESTING TOOLS

Critical factors for test automation success
Types, examples of automated tools
Test execution tool considerations
Action-based frameworks aid flexibility

DETAILED TEST PLANNING

IEEE Standard on Unit Testing
Functional (Black Box) testing strategy
3-level top-down test planning and design
Exercise: Functionality matrix
Use cases, revealing overlooked conditions
Exercise: Defining use case test coverage
Detailed Test Plan technical document

MEASURING AND MANAGING TESTING

Defect reports that prompt suitable action
Projecting when software is good enough
Measuring testing effectiveness

Top