Examine the Design Documents & Code
- These are static, white box techniques.
- Handling these requires some programming expertise.
- It is best if the testers know the language in which the software is written.
- Consequently, you often find these tests are run by either Programmers with software testers as observers or Software testers with help from the programmers.
Major Problems with These Tests
They are often NOT performed! 未運行
These are the hardest to justify to upper management as they are viewed by many as too time consuming.
Some of the problem is the perception that programmers are not productive if they are not generating code.
Note: The tyranny of the LOC metric, Lines of executable code as a measure of productivity!
Three approaches
Formal inspection
Peer review
Walkthrough
Formal reviews
These are structured processes for doing static, white box testing.
4 elements are required:
- Identify problems by directing attention to the code, not who wrote it.
- Setup and follow rules for the review:
- How much code should be examined?
- How long should the review take?
- What is fair game for the review?
- Prepare and assign duties to people
Moderator, recorder, reader, etc. - Write a report.
These are not just “get together and go over code” sessions!
Relative strengths of test strategies
