Report current as of: 05/30 16:30:57
This report shows how test sessions map to coverage areas. All numbers except Bugs and Issues represent normal sessions. A normal session is about 90 minutes of uninterrupted test time by a single tester. If the Total column reports "15" for a particular area, it means that the specified area was mentioned on session reports that totaled to a duration equivalent to 15 normal sessions worth of testing. A coverage area is entered in the #AREAS section of a test session report only if the test lead verifies that a substantial part of the session covered that area. Thus, this is a rough, but meaningful indication of test coverage from a tester's perspective.
| TOTAL | CHTR | OPP | TEST | BUG | SETUP | BUGS | ISSUES | AREA |
| 13 | 12.73 | 0.26 | 7.48 | 3.19 | 2.05 | 32 | 18 | BUILD | 1.2 |
| 13 | 12.73 | 0.26 | 7.48 | 3.19 | 2.05 | 32 | 18 | OS | WIN98 |
| 5.33 | 5.13 | 0.2 | 2.33 | 2 | 0.79 | 20 | 7 | DECIDERIGHT | MAIN TABLE WINDOW |
| 4.33 | 4.26 | 0.06 | 1.42 | 1.78 | 1.05 | 17 | 5 | DECIDERIGHT | QUICKBUILD |
| 3.99 | 3.99 | 0 | 1.73 | 1.33 | 0.93 | 7 | 6 | STRATEGY | CLAIMS TESTING |
| 3 | 2.8 | 0.2 | 1.1 | 1.13 | 0.56 | 14 | 2 | STRATEGY | COMPLEX | STRESS TESTING |
| 2.66 | 2.66 | 0 | 0.79 | 1.06 | 0.79 | 7 | 3 | DECIDERIGHT | OLE |
| 2.66 | 2.66 | 0 | 0.79 | 1.06 | 0.79 | 7 | 3 | DECIDERIGHT | DOCUMENTS WINDOW |
| 1 | 1 | 0 | 0.3 | 0.6 | 0.1 | 6 | 2 | STRATEGY | COMPLEX | FLOW TESTING |
| 2 | 1.8 | 0.2 | 0.9 | 0.54 | 0.36 | 8 | 2 | STRATEGY | COMPLEX | FUNCTION & DATA TESTING |
| 1.33 | 1.33 | 0 | 0.93 | 0.26 | 0.13 | 0 | 3 | STRATEGY | COMPLEX | RISK TESTING |
| 5 | 4.93 | 0.06 | 4.35 | 0.12 | 0.46 | 5 | 8 | STRATEGY | EXPLORATION & ANALYSIS |
| 0.66 | 0.6 | 0.06 | 0.42 | 0.12 | 0.06 | 4 | 2 | DECIDERIGHT | REPORT GENERATOR |
| 1.33 | 1.33 | 0 | 1.33 | 0 | 0 | 0 | 2 | DECIDERIGHT |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | DECIDERIGHT | ADVISOR |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | DECIDERIGHT | BASELINE |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | DECIDERIGHT | CATEGORY LABEL EDITOR |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | DECIDERIGHT | CRITERIA WEIGHTS WINDOW |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | DECIDERIGHT | DECISION TABLE |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | DECIDERIGHT | GRAPHS |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | DECIDERIGHT | IMPORT / EXPORT |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | DECIDERIGHT | INPUT OPTIONS |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | DECIDERIGHT | PRINTING |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | DECIDERIGHT | SCENARIO MANAGER |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | DECIDERIGHT | SENSITIVITY INDICATORS |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | DECIDERIGHT | START-UP WINDOW |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | DECIDERIGHT | UI |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | DECIDERIGHT | USER MANUAL |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | DECIDERIGHT | WEIGHTING |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | DECIDERIGHT | PREFERENCES |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | OS | WINDOWS2000 |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | OS | WINNT |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | STRATEGY | BUG REGRESSION TESTING |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | STRATEGY | CAPABILITY TESTING |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | DECIDERIGHT | OPTIONS RATINGS |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | DECIDERIGHT | OPTION RATINGS WINDOW |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | DECIDERIGHT | ONLINE HELP |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | DECIDERIGHT | NUMERIC EDITOR |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | DECIDERIGHT | LANGUAGE ELEMENTS |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | STRATEGY | COMPLEX | STRUCTURE TESTING |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | STRATEGY | COMPLEX | USE CASE TESTING |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | DECIDERIGHT | INSTALLATION |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | STRATEGY | PERFORMANCE TESTING |
| 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | STRATEGY | TRAINING |
The total amount of session work, expressed in normal sessions, that is associated with a coverage area. If the Total column reports "15" for a particular area, it means that the specified area was mentioned on session reports that totaled to a duration equivalent to 15 normal sessions worth of testing. Not that you cannot add totals from different areas, since session totals from different areas may well have sessions in common.
The total amount of session work that was within the charter of each session. This value plus the Opportunity value should equal the total amount of session work associated with the corresponding coverage area. CHTR + OPP = TOTAL
The amount of session work that was not within the charter of each session. This work may or may not have been associated with the corresponding coverage area. All we know is that the work was off the subject of the specific charter. A disproportionately high ratio of off-charter to on-charter work in a particular coverage area may represent that another test area related to this one may be distracting the testers. CHTR + OPP = TOTAL
The amount of on-charter work that was devoted to searching for bugs. The higher this value, the more time was spent by testers productively testing. Note that some product areas are much more testable than others, so 10 sessions of testing in one areas may not have the same value as 10 sessions in another. TEST + BUG + SETUP = CHTR.
The amount of on-charter work that was devoted to investigating and reporting bugs. This work is only reported if it interrupts bug searching. Thus, the fewer problems there are, or the easier they are to investigate, the lower this value will be, and the more testing will get done. TEST + BUG + SETUP = CHTR.
The amount of on-charter work that was devoted to anything other than bug searching or bug investigation and reporting. This work is only reported if it interrupts bug searching. Typically this category includes gathering information for testing, setting up equipment, or filling out the session reports. Thus, the more organized the test process is, the lower this value will be, and the more testing will get done. Chronically high setup values probably indicate that the test project is still getting up to speed. TEST + BUG + SETUP = CHTR.
The total number of bugs reported to the test lead that are associated with this coverage area. Not every bug reported to the test lead will be proper to report in the bug tracking system. A high ratio of BUGS to TEST generally indicates either a weak area of the product, or an area that confuses the testers.
The total number of issues reported in sessions associated with the coverage area. A high ratio of ISSUES to CHTR generally indicates a testability problem in that area.
The coverage area to which the metrics apply. What we call "coverage areas" goes beyond areas of the product itself. Types of testing, build numbers, and platforms are also reported. However, mostly the areas correspond to functional, structural or data elements of the product. These areas are predefined and controlled by the test lead. We selected these specific areas to allow reasonably granular reporting while not getting so granular that the accuracy suffers.