The Reliabity Ratios view list coverage metrics and statistics about each class and test class that has been selected to be run in GERT.
The Metrics Total box contains the following metrics (LOC represents lines
of code):
- Test Cases / Source LOC (M1): is an indication of whether there are
too few test cases written to test the body of source code;
- Source LOC / Test LOC (M2): is an indication of whether the ratio
M1 was misleading as there might have been fewer, but comprehensive,
test cases;
- Assertions / Source LOC (M3): serves as a crosscheck for both M1 and
M2 because there are few test cases but each have a large number of
assertions;
- (Test LOC / Test Classes) / (Source LOC / Source Classes) (M4): is
used as an indicator for estimating defect density when prior releases
of the software are available so that any change in the relative class
size can be analyzed to determine if the increase in the size of the
class has be accompanied by a corresponding increase in the testing
effort;
- Source LOC / Requirements (M5): is an indication of the program size
with respect to the requirements;
- Weighting of Conditionals for Source / Weighting of Conditionals for
Test (M6):is an indication of the extent to which conditionals are used.
The use of conditional statements increases the amount of testing required
because there are more logic and data flow paths to be verified ;
- Overall Statement Coverage: A percentage of all the LOC in the source
file that are run by a test. measures test coverage and serves as a
cross checks to M1, M2, and M3 to make sure that the same part of the
code does not get tested repeatedly
- Overall Branch Coverage: The percentage of branches (paths through
conditional code) in the source course tested.
The colors of the text in the Metrics Totals box describes if the metric is within, above, or below required bounds. The color can be changed in the GERT preference.
The Source Classes area contains statistics about an individual selected source files including LOC, classes (there is more that one class listed if there are inner classes), conditionals, statement coverage percentage, and branch coverage percentage.
The Test Classes area contains statistcs about an individual selected test file including LOC, classes (there is more than one class listed if there are inner classes), test methods, and asserts.
Note: In order to switch between GERT and running JUnit tests, make sure that jcoverage.jar (located in the GERT plug-in directory) is on your project's build path. If there are any other errors, change your code and resave, thus recompiling your code. You should be able to run JUnit then. If you have any other problems, select Project > Clear.... |
. 
in the Reliability Files view allows you to remove files, run a coverage sweep, and refresh the coverage report. The first icon removes a selected file. The second icon removes all of the files. The down arrow contains options to remove just source and test files, and run/refresh the coverage report.