|
printer-friendly
Intermediate
Software Testing
Techniques
3
Days
This
course is designed for software testers that
want to go deeper than the basic concepts. Attendees will
learn how to
create an effective test strategy, how to design creative test cases,
how to
optimize test cases to get the most testing from the fewest number of
cases and
how to measure and report the results of testing.
Attendees
will leave this course with a solid foundation for testing in
situations which are very diverse and dynamic.
This
course is centered around a common case study which builds throughout
the course.
Intermediate
Software Testing Techniques will
help you
reach the next level in your testing skills. You will emerge from this
three-day session knowing how to plan and conduct tests in diverse
and complex environments.
Objectives
This course will build on basic
testing principles and introduce new methods to teach testers how to:
- Describe the major software
development lifecycles and how testing fits into those methodologies
- Develop a test strategy
- Write a high-level test plan
- Develop test scripts and test
cases using a wide variety of techniques
- Create decision tables
- Get the most testing from the
least number of test cases
- Track and control test scripts
and cases
- Assess risk from the project,
technical and business perspectives
- Describe which tools are the
best to use in a particular test
- Describe effective test tools
available
- Write meaningful test reports
- Measure your testing efforts
- Use the results from testing to
improve the testing process and other processes
Who Will Benefit
- Test
analysts
- Testers
- Test
engineers
- Software
developers
- Project
managers
- Test
lab managers
- QA
analysts
The program requires basic testing
knowledge or experience.
Program Information
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
organization.
Content and
Structure
Module
STBD - Test Planning Overview: Strategies and Tactics (1.5 hrs.)
- Basic
Testing Principles
- Why
Is It Important That Testing Uses A Process?
- Process
Benefits
- The V
Diagram
- What
is a Test Strategy?
- The
Components and Format of a Test Strategy
- Identifying
Critical Success Factors
- Sample
Test Strategy
- Defining
Test Objectives
- Sample
Test Objectives
- Major
Elements of a Test Plan
- Planning
Time Guidelines
- Tips
for Test Planning
Module
ISTA - Intermediate Test Design Strategies (1.5 hrs.)
- How
Much Effort Should Be Dedicated to Test Design and Types?
- Tests
by Type of Project
- Test
Case Economy
- How
to Match the Test to the Project and Test Stage
- Rules
for Test Applicability
- Producer
Testing
- Customer
Testing
- Automated
Test Strategies
- Test
Cases
- Test
Case Types
- How
to Document Test Cases
- Organizing
the Test Cases
- The
Decomposition of Test Cases from Test Objectives and
- Functions
- A
Test Case Design and Tracking Tool
- Sample
Test Cases
- Test
Case Best Practices
- How
to Be Creative in Test Case Design
- Types
of Test Cases
- Functional
Test Cases
- Structural
Test Cases
- Regression
Test Cases
- Security
Test Cases
- Performance
Test Cases
- Interoperability
Test Cases
- Compatibility
Test Cases
- Portability
Test Cases
- Usability
Test Cases
- Scalability
Test Cases
- End-to-end
Testing
- Batch
Test Cases
- Conversion
Test Cases
- Link
Test Cases
- Browser
Test Cases
- Exploratory
Testing
- Parallel
Test Cases
- Vendor
Test Cases
- Test
Cases by Phase
- Unit
Test Cases
- Integration
Test Cases
- System
Test Cases
- Acceptance
Test Cases
Module
ISTB - Intermediate Test Case Design Techniques (6 hrs.)
- Orthogonal
Arrays
- What’s
the Need?
- What
is Orthogonality?
- The
Fault Model Behind Orthogonal Array Testing
- Double-mode
Defects
- What
Research Indicates
- The
Likelihood of Triple-mode or Higher Defects
- What
Common Sense Indicates
- The
Value of Designing Tests With Orthogonal Arrays
- Terminology
- Orthogonal
Notation
- Orthogonal
Array – Example
- Facts
About Orthogonal Arrays
- The
Good News
- A
Process for Applying Orthogonal Arrays
- An
Example
- Exercise
– Build an Orthogonal Array for Case Study Exercise
- Sample
Orthogonal Arrays
- The
Allpairs Algorithm
- Tools
for Pairwise Testing – Allpairs
- A
Word of Warning About Pairwise Testing
- Review
– How Do Orthogonal Arrays and Pairwise Testing Help?
- Resources
for Orthogonal Arrays and Pairwise Testing
- Decision
Tables
- Decision
Table Example
- Decision
Table Example (Cont’d.)
- Decision
Table with Three States
- How
Decision Tables Help in Test Case Design
- How
Decision Tables are Derived
- Reducing
Decision Tables Example
- Why
Reduce Tables?
- Expanding
Decision Tables
- Why
Expand Tables?
- How
do Organizations Use Decision Tables?
- Cause-Effect
Graphing
- The
Cause-Effect Graphing Process
- Cause-Effect
Graphing Symbols
- Cause-Effect
Graphing Example
- Helpful
Tips for Decision Tables
- Test
Cases from Use Cases
- Use
Cases
- Use
Case Components
- The
Use Case to System Test Case Process
- More
About Use Cases as Test Cases
- Functional
Test Cases – Requirements-based Cases
- The
Process for Decomposing Requirements into Test Cases
- Benefits
of the Process
- Overview
of the Process
- Requirement
Specification to System Test Case Process Approach
- Process
Tailoring
- Exercise
- Conclusions
About the “Requirements to Test Case”
Process
- How
to Maximize Requirements Coverage
- Example:
Maximizing Requirements Coverage
- Can
the Number of Test Cases be Reduced?
- A
Redundant Test Case
- Change
the Outcome with One Simple Change
- Tests
Based on Business Scenarios
- Tests
Based on Business Scenarios – Example
- Test/Cycle
Matrix
- Sample
Test/Cycle Matrix
- What
is a Test Cycle?
- Why
Use Test Cycles?
- Traditional
Test Cycle
- Functional
Test Cases – Behavioral
Module
UATD - Risk Assessment (1 hr.)
- What
is Risk?
- The
Nature of Risk
- The
Three Views of Risk
- The
Elements of Risk
- Risk
Assessment
- Why
is Risk Assessment Important?
- Computer
System Risks
- Three
Views of Project Risk
- Assessing
Technical Risks
- Likelihood
of Failure
- Impact
of Failure
- A
Sample Risk Chart
- Practical
Application
- Ways
to Apply the Results
- Example:
Applying the Results
- Assessing
Business Risk
- Sample
Business Risk Chart
- How
Can This Information Be Used?
- When
is Testing Complete?
- A
Problem in Risk-Based Testing – Cases that Span Risk Levels
- When
is Risk Assessment Performed?
- Who
Performs Risk Assessment?
- Who
Owns Risk Assessment?
- Additional
Resources
Module
IQAF - Test Tool Overview (1 hr.)
- Working
Definition of a Test Tool
- Risks
of Not Automating Testing
- Risks
of Automating Testing
- The
Role of Test Tools
- Manual
Testing
- Automated
Testing
- The
Major Issues
- “Top
10” Test Tools
- Interactive
Test/Debug
- Capture/Playback
- Version
Control
- Stress
and Load Testing
- Defect
Tracking
- Memory
Testing
- Test
Management
- Coverage
Analyzers and Thread Testers
- Checklists
- Critical
Success Factors
- Closing
Thought
Module
ISTD - Performance Testing (1.25 Hrs.)
- Key
Concerns
- The
Challenge
- Hitting
the Performance Wall
- Performance
Testing
- Terminology
- Prerequisites
- Type
of Technology
- An
E-Commerce Schematic
- Client/Server
Load Testing
- Manual
vs. Automated Tools
- Which
Tools are Applicable?
- How
Can Tools Help?
- Common
Problems and Pitfalls
- Memory
Leaks
- Anatomy
of a Boundary Violation
- Anatomy
of a Memory Leak
- How
to Test for Memory Leaks
- Bounds
Checkers
- Example:
NuMega Bounds Checker Interface
Module ISTF - Intermediate Test Evaluation and Analysis
(1.5 hrs.)
- Test
Evaluation Workbench
- An
Evaluation Toolkit
- A
Testing Dashboard
- Statistical
Methods
- Example
- Sample
Control Chart
- Example
– Standard Deviation
- Example
– Computing the Control Limits
- What
Does This Tell Us
- How
to Go Forward
- Common
Causes vs. Special Causes
- How
to Measure Test Coverage
- Requirements
Coverage
- Adding
Traceability
- Requirements
and Test Case Coverage
- Tools
for Test Case Design from Requirements
- Requirements
and Test Case Coverage
- Business
Process Coverage - The Test/Iteration Matrix
- How
to Capture Test Results
- How
to Manage the Level of Measurement Intrusiveness
- Comparison
Tools and Techniques
- How
to Build a Robust Testing Baseline
- Regression
Testing – Comparing to a Baseline
- How
to Create and Maintain Baseline Test Data
- Test
Baseline Data Cycle
- Regression
Testing – Maintaining the Baseline
- How
to Analyze and Make Sense of Test Results
- Comparison
to the Baseline: Correctness
- Tracking
to Current Project Goals
- Comparison
to Past Projects
- Comparison
to Estimates
- How
to Present Complex Information in Understandable Ways
- Continually
Improving the Process
- The
Goal/Question/Metric Paradigm
- Identifying
Needs and Goals
- Answering
the Right Questions
- Critical
Success Factors
- Exercise
- Develop Your Own Action Plan for Improvement
Module
TTLF - Metrics and Measurements (1 Hr.)
- Terminology
- Valuable
Test Measurements & Metrics
- Benefits
of Testing Metrics and Measurements
- What
Needs to be in Place to Capture Measurements and Metrics
- Tools
and Techniques for Measuring Testing Activities
- Why
Track Defects?
- Tracking
and Understanding Defect Trends
- The
Role of the Defect Administrator
Module
STBI - Test Evaluation and Reporting (1 hr.)
- Prerequisites
for Test Evaluation
- Test
Evaluation and Reporting Process
- What
Test Reporting Should Be
- Types
of Test Reporting
- System
Test Evaluation - Defect Reporting
- The
Defect Life Cycle
- Defect
Tracking - Things You Need to Know
- Sample
Defect Categories
- Sample
Defect Priorities
- Status
Reporting
- Final
Reporting
- Test
Summary Report
- How
Can This Data be Used?
- Final
Thought
Resources
- Checklists
and Templates
- Glossary
- Bibliography
Deliverables
- Course
notebook with slides, worksheets, checklists, complete examples and
supporting text
- You will have the basic information needed to
plan and execute an effective test of a software application.
All materials on this site
copyright 1996 - 2008, Rice Consulting Services, Inc.
Rice
Consulting Services, Inc.
P.O. Box 892003
Oklahoma City, OK 73189
405-691-8075
"Leaders
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
browser!
|