tests/unit/README: describe how to unit test static functions#21018
Merged
tests/unit/README: describe how to unit test static functions#21018
Conversation
3c8f7ff to
2df0048
Compare
There was a problem hiding this comment.
Pull request overview
Updates the unit test README to document how to unit test libcurl internal functions that are static in normal builds by using the UNITTEST macro and the generated lib/unitprotos.h.
Changes:
- Added a “Testing static functions” section explaining
UNITTESTvsstatic. - Documented the requirement to provide a
UNITTESTprototype so the unit-prototype extraction can generatelib/unitprotos.h. - Included a small illustrative example.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
UNITTEST explained Closes #21018
713f91d to
2b3332e
Compare
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.
UNITTEST explained