...
The RCS compabitilty tests consist of checking that the software interface is compliant with the RCS ICD specification (see ROC-PRO-PIP-ICD-00037-LES available in ROC Documents).
The tests are run performed using dedicated instances of the ROC-SGSE and RODP, deployed on the roc-dev.obspm.fr server.
An instance Moreover, instances of the RIVP will be made available to the teams to test their software interface compliance, before deliverying to the ROC.
The way to use this instance thes instances is described in the RIVP "RCS Interface Validation Pipeline User Manual" (will be provided soon).
| Warning |
|---|
|
RCS INTEGRATION TESTS
The RCS integration tests are performed by the ROC team, using representative enough RCS input/ouput "test" data samples; one set of files for each RCS data product.
The tests consist of calling the RCS with a "pre-prod" instance of the ROC pipelines, in order to re-produce at the LESIA the "test" data.
The "test" data samples shall be delivered by the RCS teams, in collaboration with the ROC, as specified in the REGU (see ROC-GEN-SYS-NTT-00019-LES in the ROC Documents).
The RCS integration tests consist of running the RCS on a "pre-prod" instance of the ROC pipelines
...
The ROC team can however help the teams to identify and supply the input "test" data (for instance, some L2 and L1R output data CDF require input L1/HK CDF that can only by generated by the ROC pipelines).
| Warning |
|---|
|
RCS VALIDATION TESTS
The RCS validation tests shall allow the ROC to validate the requirements and specification related to the RCS and their data products.
TBW