Add test-specific mock include directives macros#830
Open
JannisRln wants to merge 1 commit intoThrowTheSwitch:masterfrom
Open
Add test-specific mock include directives macros#830JannisRln wants to merge 1 commit intoThrowTheSwitch:masterfrom
JannisRln wants to merge 1 commit intoThrowTheSwitch:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds new no-op configuration macros for Unity/CMock test executables to allow tests to declare additional headers that should be included in generated mocks.
The new
TEST_MOCK_INCLUDE(mock, header)macro provides a simple way to associate an extra header with a generated mock, for example:TEST_MOCK_INCLUDE("mock_driver.h", "test_driver_types.h")This also adds location-specific variants for finer include placement control:
Motivation
Some generated mocks require additional type or dependency headers to be included in a specific location. Providing explicit macros for this allows test executables to declare those requirements without modifying generated files manually.
I preparing a Pull Request in Ceedling to support this feature. Ceedling PR 1139