Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhance unit test to check for reset of values on initialization (requirements related) #1969

Closed
skliper opened this issue Sep 21, 2021 · 0 comments · Fixed by #1970 or #1967
Closed
Assignees
Milestone

Comments

@skliper
Copy link
Contributor

skliper commented Sep 21, 2021

Is your feature request related to a problem? Please describe.
It's difficult functionally (or via CTF) to confirm the reset requirements related to counters/states since they get populated/used and counters increment based on the configuration.

Requirements that would help to check in coverage tests:
cSB4500 - SB: Initialize Routing On Power On Reset | Upon a Power-on Reset the cFE shall initialize the Routing Information and clear all error counters.
cSB4501 - SB: Initialize Routing On Processor Reset | Upon a Processor Reset the cFE shall initialize the Routing Information and clear all error counters
cTIME2002 - TIME: Zero Counters | Upon receipt of Command the cFE shall set to zero all counters reported in Time Services telemetry.

Describe the solution you'd like
Add a quick assert that the values do get initialized (typically in CFE_*_EarlyInit) as required.

Describe alternatives you've considered
None

Additional context
None

Requester Info
Jacob Hageman - NASA/GSFC

@skliper skliper added this to the 7.0.0 milestone Sep 21, 2021
@skliper skliper self-assigned this Sep 21, 2021
astrogeco added a commit that referenced this issue Sep 21, 2021
Fix #1969, Confirm sb/time reset requirements in coverage test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant