Shared module uncovered branch due to run time logic based on compile time config

[skliper]

Is your feature request related to a problem? Please describe.
Run time logic for compile time config example:

osal/src/os/shared/src/osapi-module.c

Lines 98 to 100 in cb95655

	OS_static_symbol_record_t *StaticSym = OS_STATIC_SYMTABLE_SOURCE;
	while (StaticSym != NULL)

Full branch coverage of while loop requires both OS_STATIC_SYMTABLE_SOURCE set to NULL and non-NULL.

Note by design the build system has a 1 to 1 to 1 relation - code/ut code/test exec, so an extra build would break the pattern.

Describe the solution you'd like
Possibilities:

• break build pattern and build additional "special" test w/o OS_STATIC_SYMTABLE_SOURCE defined
• source selection based on compile time config (or utilize preprocessor)
• add a function to set and/or get the static symbol table pointer
• build/run twice from the test procedure... once with the definition removed from the unit-test-coverage CMakeLists.txt

Describe alternatives you've considered
None

Additional context
Coverage testing

Requester Info
Jacob Hageman - NASA/GSFC

[jphickey]

IIRC the whole logic behind the separate OS_STATIC_SYMTABLE_SOURCE definition was so that the coverage test could provide its own definition of the static sym table.

osal/src/unit-test-coverage/shared/CMakeLists.txt

Line 60 in cb95655

"OS_STATIC_SYMTABLE_SOURCE=OS_UT_STATIC_SYMBOL_TABLE"

It should also (theoretically) be possible to make this a pointer which can be NULL as well, so UT can simply have two test cases, one for NULL and one for non-NULL. I can experiment but I think it is probably doable.