2 to the particular
software bugs. See [Wei-Tek] for details of a minimal approach to test coverage of embedded medical
devices complete with examples and toolkit.
2.8.2 System Test Coverage Strategies
Here are three approaches:
1. Major features first. Create tests which will exercise all the principal features first, to give maximum
coverage. This will probably be the same as the regression test. Then exercise each feature
in some depth.
2. Major use cases first. As major features. Requires that you know both the user profile and the use
profile. The test must be end-to-end such that some real-world user objective is reached.
3. Major inputs and outputs. If the application is I/O dominated, then identify the most common
kinds of inputs and outputs and create tests to exercise them.
These can be followed by:
1. All GUI features
2. All functions with variations
3. All input/output combinations
Note that various test management tools will give you coverage metrics showing the proportion of
requirements ???covered??? by a test, test cases run,
etc. These are of course purely arbitrary; just because a
tester has associated a test case to a requirement doesn??™t mean that the requirement has been adequately
covered. That??™s one of the things you as test manager must check.
28
Manage Software Testing
2.9 Are There Any More Embarrassing Questions?
At some point management may start to look seriously at their costs.
Pages:
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135