Training
Improving the Effectiveness of Testing
|
Many organizations have conflicting goals and objectives for testing
software. For example, some organizations believe the purpose of
testing is to show that the software works. We know from over three
decades of experience that testing can only be used to show
the presence of defects, not prove their absence.
Further compounding the problem is a lack of understanding of the
levels of testing and the different methods that are appropriate at each
level as illustrated below: |
|
Level |
Objectives |
Performed by |
Environment |
Test Methods |
Unit or Module Testing |
Verify logic, data, and algorithms in individual modules | Software Engineering | Isolated. | White Box |
Integration Testing |
Verify interfaces between modules | Software Engineering | Isolated and/or simulated. | White Box, Top-down, Bottom-up, or Outside-in |
Validation Testing |
Determine if the software meets requirements in SRS | SQA or Software Validation Team | Actual | Functional, White Box, and Act-Like-A-Customer |
Regression Testing |
Determine if software still meets requirements in light of bug fixes or changes | SQA or Software Validation Team | Actual | Functional and Act-Like-A-Customer |
Acceptance Testing |
Determine if system meets customer requirements | SQA or Software Validation Team | Actual. Usually with customer present | Functional and Act-Like-A-Customer |
|
One way to improve the effectiveness of testing involves using a test method
called Act-Like-A-Customer testing (or ALAC) which is based on the
following simple principle:
|
|
|
|
By working with your Software QA staff, I can help them improve the
effectiveness of the tests they write by learning the technique of
Act Like A Customer testing. In this way, the tests they develop are
more likely to uncover problems your customers would likely find.
Improving the effectiveness of testing helps improve Customer Satisfaction
and therefore provides a significant return on investment.
|
|
Tailoring
|
|
|
|
This workshop can be tailored to meet your specific needs. This informal, interactive workshop is based, in part, on the book: Software Verification and Validation for Practitioners and Managers, by Steven R. Rakitin. |
For further information,
call Steve Rakitin at 508.529.4282
or e-mail him at
steve@swqual.com
| Home |
Company Info |
Contact Info |
Food for Thought and Predictable Software Development are trademarks of Software Quality Consulting, Inc.
Updated January 2008
Copyright ©2008 Software Quality Consulting, Inc. All rights reserved.