R1 Information

MONTHLY-2004-01

ATTENTION: starting from January 2004 we have changed the method for counting the SLOC and preparing the graphs.

Note: the XML files have been removed. Note also that instead of calculating the percentage of test LOCs against src+test, we calculate the test LOCs against the src LOCs.

You will have a page with the results per each subsystem (see list below). In this page of results, there is a table with 3 columns:

- the first one lists the modules belonging to the subsystem,

- the second gives the results of the tests (PASSED, FAILED, UNDETERMINED, when it is neither PASSED nor FAILED); sometimes the test directory can be missing, so you will just see the message: "No test directory, nothing to do here".

- the third one gives a resume produced by Purify/Coverage reporting the analysis results on:

The values reported for every item in the list above give the number of hits for that item.

In the same cell with the resume there is a link to the "Complete Report" produced by Purify. In the Complete Report one has information about the lines where the hit happened. For a loop, one has also the values: 0 (the loop is executed without entering into it), 1 (the loop is entered once), 2+ (the loop is entered and repeated once or more times).

Sometimes, instead of the resume, you will see a message like:

ERROR: No coverage info available
No atlout.spt

This happens when the modular test of that module is a fake one (for example the test is actually just an "echo something"), so there is no code (Java, Python or Cpp) that can be instrumented. We found in total 12 such cases, 11 in ACS, 1 in ARCHIVE.

ACS