has three distinct activities: Planning, execution and evaluation. Each
activity requires about one-third of the time and effort. However, how
well you do the one-third of the time in test planning determines how
well the other two-thirds of the testing effort will be performed.
course teaches how to write test
plans that make the best use of your resources. We discuss many aspects
of testware and how to create, maintain and manage it through all the
phases of testing on a project.
"Testware" is a term used to describe all of the materials used to
perform a test. Testware includes test plans, test cases, test scripts,
and any other items needed to design and perform a test. Designing
tests effectively, maintaining the test documentation, and keeping
track of all the test documentation (testware) are all major challenges
in the testing effort. This course is designed to teach the process of
dealing with all aspects of testware before, during and after the test.
Designers and Analysts
the most out of your existing investment in testing and how to leverage
the key issues in developing testware.
how to design tests that adequately cover requirements and business
your career by reinforcing your testing expertise.
This course is presented on an in-house basis only unless offered as a
special public course. Contact
us for information about how to bring this course into your
1 - Terminology
Deming Workbench Model
2 - Developing Quality Requirements
Importance of Requirements
Importance of Inflection
Importance of Word Meanings
Right People - Who Do We Involve?
to Control Change
Considerations For Existing Software Requirements
Role Playing the Requirements Process
3 - Basic Test Planning
Basic Testing Process
is a Test Strategy?
Components and Format of a Test Strategy
Critical Success Factors
Components and Format of a System-level Test Plan
Elements of a Test Plan
Much Time Should be Spent on Test Planning?
for Test Planning
4 - The Test Planning Process
Test Planning Components
Test Planning Tasks
1 - Develop Test Strategy
2 - Define Test Objectives
3 - Identify Needed Test Resources
4 - Plan Test Environment
5 - Define Test Procedures
6 - Identify Functions To Be Tested
7 - Identify Interfaces With Other Systems or Components
8 - Write Test Scripts
9 - Define Test Cases
10 - Design Test Data
11 - Build Test Matrix
12 - Determine Test Schedules
13 - Assemble Information
14 - Finalize the Plan
5 - Knowing What’s Important: Risk Assessment
- Test Case Development
is Risk Assessment Important?
Elements of Software Risk
Informal Risk Assessment Process
More Formal Risk Assessment Process
Test Planning Components
to Document Test Cases
of Test Case Design Techniques
Threads Based on Business Scenarios
is a Test Cycle?
Use Test Cycles?
Test Coverage Levels
Test Cases – Behavioral
7 - Unit Testing
is Unit Testing?
is Unit Testing Performed?
Much Preparation is Necessary?
Create a Unit Test Plan?
Test Case Design - Functional Tests
Test Case Design - Structural Tests
Unit Test Process
to Document Functional Unit Test Cases
to Design Structural Tests
to Document Unit Interfaces
Test Execution - Procedural Software
Test Execution - Event-driven Software
Test Execution - Case-developed Software
Methods for Unit Testing
Methods of Unit Testing
Test Defect Reporting
Test Summary Report
8 - System Testing
is System Testing?
System Test Objectives
System Functions to Test
System Test Scripts
System Test Cases
for Performance Testing
the System Test Matrix
System Test Schedules and Resources
the System Test Plan
Representative System Test Plan Outline
Methods of System Testing
9 – Tools For Testware Creation and Management
Your Own Tools
- How Do the
Tools Work Together?
10 – The Testware Lifecycle
- Step 1 –
Testware Design and Creation
- Step 2 –
Review and Pre-Test
- Step 3 –
Perform Test and Refine
- Step 4 –
Report Test Results
- Step 5 –
Perform Ongoing Maintenance to Testware
notebook with slides, worksheets, checklists, complete examples and
All materials on this site
copyright 1996 - 2009, Rice Consulting Services, Inc.
Consulting Services, Inc.
P.O. Box 892003
Oklahoma City, OK 73189
are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that is
worthwhile." -- Vince Lombardi
This site best
viewed with the Mozilla Firefox