-
Notifications
You must be signed in to change notification settings - Fork 203
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
Scrub for discrepancies between implementation return codes and documentation #1724
Comments
Got the script running against CFE test logs, first set of results/issues for ES (unfortunately kind of a long list to look at): CORRECTION - original list I posted was just the coverage logs. This updated set includes both coverage and functional test - results are better, but still a bunch missing.
|
First pass at API doxygen scrub, this updates the in/out markings on parameters where they were not correct, and adds nonnull and nonzero tags where appropriate.
First pass at API doxygen scrub, this updates the in/out markings on parameters where they were not correct, and adds nonnull and nonzero tags where appropriate.
First pass at API doxygen scrub, this updates the in/out markings on parameters where they were not correct, and adds nonnull and nonzero tags where appropriate.
First pass at API doxygen scrub, this updates the in/out markings on parameters where they were not correct, and adds nonnull and nonzero tags where appropriate.
Partial #1724, update in/out status and nonnull/nonzero tags
#1833 is in integration-candidate now |
Adds SB functional test cases to cover all missing items that were identified as part of the scrub in issue nasa#1724. Where a specific condition is not testable because it requires a failure of another subsystem, it is marked as `covtest` to indicate it is only verifiable in coverage test environment.
Adds ES functional test cases to cover all missing items that were identified as part of the scrub in issue nasa#1724. Where a specific condition is not testable because it requires a failure of another subsystem, it is marked as `covtest` to indicate it is only verifiable in coverage test environment.
Adds FS functional test cases to cover all missing items that were identified as part of the scrub in issue nasa#1724. Where a specific condition is not testable because it requires a failure of another subsystem, it is marked as `covtest` to indicate it is only verifiable in coverage test environment.
Adds TBL functional test cases to cover all missing items that were identified as part of the scrub in issue nasa#1724. Where a specific condition is not testable because it requires a failure of another subsystem, it is marked as `covtest` to indicate it is only verifiable in coverage test environment.
After all above fixes/improvements, here are the remaining outstanding issues from the scrub For EVS: #1817 These remaining cases are not easily implemented with the current framework. Some need a secondary test app (see #1761), some need a state that is not under direct control of the test |
Is your feature request related to a problem? Please describe.
Need to perform a general scrub of API documentation for parameters, error checking, and and return codes, as was done for OSAL.
Describe the solution you'd like
@retval
clause.@retval
clause also have a test case that covers them@nonnull
or@nonzero
where applicableAdditional context
See nasa/osal#980
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: