The primary spreadsheet has a set of tabs showing:
???
containing details of sets of tests extracted from TestDirector?„?
FIGURE 8.29 Bug sources
7 This is a way of negotiating any changes to specifications. Long before you begin system testing you can thus
ensure management is aware of the status of your inputs so they have the opportunity to get you better documents
earlier. You can also defend yourself against charges of failing to complete testing ???on time??? by showing how you
warned them of document volatility.
Sources of defects
Multi-language
support-German 1%
Coding
assistant 1%
MetaData
repository 1%
Data
feeds 2%
Other 2%
Searches 6% Coding 7% Input
parsing 9%
Major
transactions 26%
Alerts 26%
Dynamic
constraints 1%
Corrections 1%
All 2%
Test Documents 163
??? Overview containing an amalgamated view of the feature tabs
??? Charts displaying data extracted from the overview tab
The process works as discussed in the following section.
8.19.1 Setting Up the Spreadsheets
1. Open TestDirector?„?.
2. Select a test results sheet in the Test Lab tab, right-click anywhere on it and ???Select All.???
164 Manage Software Testing
3. The sheet will then be entirely chosen and you can save it as an Excel spreadsheet. Give it a name
such as ???test x??? (this example uses ???RFC 87 test set 1???).
4. Save the Excel sheet to a folder in the ???test files??? directory (in this case ???RFC 87???) overwriting any
current one and using its name.
Pages:
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350