MatcherClass support for complex matching #52
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.
Hi,
I've extended your Matcher enum with a new type: matcherClass
This way you can provide classes instead of just functions.
Also created a MatcherClass typedef for it, so the system is independent from any concrete implementation.
I did it to use hamcrest for argument checking, this way i call use all the crazy hamcrest Matchers for checking the conditions.
The usage is pretty simple after:
someMock.someFunction(cast matcherClass(endsWith("Bar")));
And as an addition I've removed the warning, if there is no munit defined, because it works with any test runner that is based on annotations. (like hexUnit https://github.com/DoclerLabs/hexUnit).
I want to modify later the macro to be able to receive configuration for the annotation and field names from outside.
I hope you like the modification.
Cheers,
Balazs