Shared Simulator 2
The monthly integration for Shared Simulator 2 has been performed based on ACS-5_0_5
The software has been tagged with SharedSimulator2-2006-08-AfterMerge-ITER-8
These are the patches we received and integrated subsystem per subsystem:
|
SUBSYSTEM NAME |
TAG (corresponding to the last bug fixing) |
|
ARCHIVE |
ACS_5_0_5-PRE-SS2-20061117 |
To validate the software delivered for R4, the tests from the validation tests suite at the ITS twiki page have been run.
A) Short summary:
|
Number |
Test |
Type |
Result |
|
1 |
MDB 0th order test |
simple test on sending monitor points to the archive |
PASS |
|
2 |
APDM test |
check on the consistency of the APDM |
PASS |
|
3 |
Control-DataCapturer test |
mini-integration test |
FAIL |
|
4 |
Optical Pointing e2e test |
e2e test processing an OP SB |
FAIL |
|
5 |
Shared Simulator e2e test |
e2e test processing an SS SB |
PASS |
|
6 |
Holography e2e test |
e2e test processing an HG SB |
FAIL |
Note: ACACORR has not been integrated together with the rest of the software during the work of the Shared Simulator 2 functional team (FBT).
Important remark: the e2e tests 4 to 6 do not have yet the validation of the ASDM produced during the test. At the moment, the validation has to be done manually by people who know enough about the ASDM, after the test has been run. If the e2e test passes, but the validation of the ASDM fails or is missing, the e2e test is marked as FAIL.
Percentage of success on the total number of tests: 50.00 %
The software produced during the Shared Simulator 2 FBT has been validated only against the end-to-end test processing a shared simulator scheduling block (SB). There has been no time to make the optical pointing and holography SBs work. Therefore, the validation is only partial.
SLOC detailed figures:
Note: Starting from Release R1.1 ITS and SE have used a common approach in calculating SLOC.
Assessment on the sufficiency of Doxygen-like in-line documentation: Graph
|
Modules inline |
Global inline
|
See the log at this link.
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:
Functions
Functions and exits
Statement blocks
Implicit blocks
Decisions
Loops
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.
Note: the Test Coverage Analysis is not yet stable. Work is in progress to improve the results. You will see errors like:
This means that the test exists and is executed but Purify is not able to dump the information collected in the result file. This error is under investigation. We had 5 cases in ACS only
still under investigation, we don't know yet the reasons
We hope to clarify the problems under investigation as soon as possible!
See the list at this link.
See details at this link.
