The bplib development branch currently does not have coverage tests implemented. This is a requirement for flight software to have this, so it needs to be implemented.
As a prerequisite to this, a test framework should be utilized to facilitate testing for coverage analysis. All other CFS components use "UtAssert" which is included as a submodule within the OSAL repository (see https://github.com/nasa/osal). However using this framework would add a hard dependency on OSAL, which would affect the standalone bplib build. Consensus needs to be made to determine if this is OK, and if so, OSAL should become the only operating system abstraction for BPLib.
Status update as of 2022-09-28, working on adding coverage tests for BPLib.
As part of this, we will need to better integrate with NASA OSAL (as this provides UtAssert and the underpinning for coverage analysis and reporting). See nasa/osal#1284 and nasa/osal#1289 as dependencies of this.
Need to better modularize some code and prune out unused code as the proper organization is necessary for stub linking - required for coverage. See #164 as dependencies.
Currently have stubs generated for all submodules, and coverage test implemented for "common" code (rb tree and CRC algorithms).
The bplib development branch currently does not have coverage tests implemented. This is a requirement for flight software to have this, so it needs to be implemented.
As a prerequisite to this, a test framework should be utilized to facilitate testing for coverage analysis. All other CFS components use "UtAssert" which is included as a submodule within the OSAL repository (see https://github.com/nasa/osal). However using this framework would add a hard dependency on OSAL, which would affect the standalone bplib build. Consensus needs to be made to determine if this is OK, and if so, OSAL should become the only operating system abstraction for BPLib.