INTEGRATION RELEASE ALMA 5.0.2
The software has been tagged with ALMA-5_0_2_12.
This report is based on tests run on the following tags: ALMA-5_0_2-6, ALMA-5_0_2_9, ALMA-5_0_2-11, ALMA-5_0_2-12
To validate the software delivered for ALMA-5_0_2, the tests from the validation tests suite at the ITS twiki page have been run. The report with the results on the tests which has been run can be found at the twiki page ALMA-5_0_2 .
Considerations about running the system end-to-end
Short overview on the test cases run in the STEs:
|
Total number of test cases available |
190 |
|
Total number of test cases executed |
101 |
|
PASSED |
78 |
|
FAILED |
23 |
|
Total number of test cases not executed |
89 |
Short overview on the Jira tickets dealt with in the STE (simulation):
|
Total number of Jira tickets about ALMA 5.0.2 |
16 |
|
Newly opened Jira tickets for ALMA 5.0.2 |
8 |
|
Old jira tickets still to be solved for ALMA 5.0.2 |
8 |
We are also collecting metrics on the test cases written and executed by ITS and the Jira tickets opened as a consequence of running the test cases. The metrics will be periodically updated. The available graphs are :
- number of test cases written and executed
- % of test cases passed and failed
- number of jira tickets opened running the test cases
SLOC detailed figures:
Note: Starting from Release R1.1 ITS and SE have used a common approach in calculating SLOC.
|
Modules inline |
Global inline
|
See the logs at this link.
For the following SUBSYSTEMS, ACS, ARCHIVE, EXEC, OBOPS, OBSPREP, OFFLINE, PIPELINE, SCHEDULING, the coverage analysis with COBERTURA has been activated.
For information about the tool, have a look at the Cobertura official web site.
CONTROL (Missing data due to te44 disk corruption)
See the list at this link.
See details at this link.