-
Notifications
You must be signed in to change notification settings - Fork 207
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
Implementation assumptions in table functional test #2506
Comments
Function that generates tables starts here in the testcase code: cFE/modules/cfe_testcase/src/tbl_content_mang_test.c Lines 278 to 378 in 37f1d28
The main issue is that it assumes a simple |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
The table functional test creates additional table files for its own use in testing. The problem is, that all of this code relies on an assumed definition/implementation of the table file structure.
In CFE there is only one "proper" source of loadable table files, and that is the build-time table generation tool (elf2cfetbl, or equivalent)
The "dump" function of table services also can create a table file, although I believe this uses a different file type so it cannot be directly loaded.
Describe the solution you'd like
At least for the test cases where the intent is to create a "good" table file but with different content, only the table generation tool should be used for this purpose. The CMake scripts have the ability to invoke the tool to produce different/alternate versions of the same table file, so this can be used.
To produce a "bad" table file where the target is a specific header, the
elf2cfetbl
tool should include extra debug options to force it to create a table with a bad value in that header. For other cases of bad values where it can corrupt data more indiscriminately, then it should work across the entire header equally.Additional context
The "bad" table tests may still pass the functional tests but could pass for the wrong reason. That is, its not guaranteed they corrupted the field they were supposed to corrupt.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: