NI-DPU ASW Static & Unit Test Report

Date Issued
2020
Author(s)
•
•
•
Bortoletto, Favio
•
BONOLI, Carlotta
•
Veri, Carlo
Abstract
Current document shows all the steps implemented during the engineering process of the DPU-ASW needed to fulfil the ESA’ Space Mission Standard C for on-board software. Both Static and Unit testing support software infrastructures were created to test the DPU-ASW source code. Both procedures were performed serialy using semi-automatic toolkits (scripts, and test suits). This document contains the first unit test report for a specific branch of the DPU ASW v0.2. A more detailed description of the adopted methodology and the used S/W for testing is provided in DPU ASW Unit Test Plan (EUCL-OPD-PL-7-004). The goal is to isolate single portions (Units) of the code and show that they work properly, which means correct S/W feedbacks to both good parameter inputs (as for the case of flight nominal operations) and to the so-called worse case, when either S/W or H/W undesired behavior is anyway expected to be treated and handled appropriately, avoiding e.g., system panic conditions. The procedure is to write test cases for all functions and methods so that whenever a change causes a fault, it can be quickly identified. Unit testing allow to find problems early in the development cycle. Among them, it is worth noticing bugs at the implementation phase and flaws or missing parts of the specification for the unit. In test-driven development (TDD) unit tests are created before the code itself is written; when the tests pass, that code is considered complete. We did not follow the TDD approach but rather, using the appropriate S/W testing tool, we started to create and develop the unit tests once the ASW reached a more consolidated evolution phase. Testing cannot catch every error in the program, because it cannot evaluate every execution path in any but the most trivial programs. Additionally, as unit testing checks the functionality of the units themselves, it will not catch integration errors or broader system-level errors (such as functions performed across multiple units, or non-functional test areas such as performance). The percentage of line coverage achieved in the unit test phase also depends on the specific functionalities of the single functions. In the case of the ASW, the nominal run-time interaction with the NISP H/W may be a further source of complexity, as the unit tests have been carried out in what can be defined as offline mode.
Uri
Rights
restricted
File(s)
Loading...
Thumbnail Image
Name

EUCL-OPD-PL-7-005 DPU ASW Static & Unit Test Report.pdf

Description
[Administrators only]
Size

1.94 MB

Format

Adobe PDF

Checksum (MD5)

868f610ab7a7983ebc9e2f193252b3ff