Fix mock callable/constructor to not accept extra configuration after… #241
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.
What:
This fixes issue 16, not allowing that extra configuration is made after
mock_callable
,mock_async_callable
or mock_constructor` receive their first call.Added tests to cover the constraint to not allow extra configuration to be made in
mock_callable
,mock_async_callable
andmock_constructor
and also validated with ad-hoc tests that TestSlide tests continues to behave as expected. As show below:For the ad-hoc tests I used this test_extra_configuration.py and invoked tests as follows:
Here are excerpts from the test results: [here]
mock_async_calable:
mock_calable:
mock_constructor: