docs(readme): document suppressing superclass calls #1444
Merged
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
Raibaz
requested changes
Oct 31, 2025
README.md
Outdated
| assertFalse(child.superCalled) | ||
| ``` | ||
|
|
||
| This approach allows you to isolate the logic within your method for unit testing without executing unwanted parent class behavior |
Collaborator
There was a problem hiding this comment.
Nit: missing the full stop at the end of the sentence :)
| To suppress a method call, especially a `super` call inside an overridden method, you can stub its behavior on a `spyk`. | ||
| Using `every { ... } just runs` replaces the entire method body, preventing the original code from executing. | ||
|
|
||
| This is particularly useful for users coming from frameworks like PowerMockito or for testing classes like Android Activities. |
Collaborator
There was a problem hiding this comment.
How about adding a link to the documentation for PowerMockito's suppress here? (https://github.com/powermock/powermock/wiki/Suppress-Unwanted-Behavior)
Contributor
Author
|
Thanks @Raibaz! 🙏 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Added a short guide to the Features section of the README explaining
how to suppress superclass method calls using existing MockK features (
spyk+every { ... } just runs).This provides a simple, built-in alternative to PowerMockito’s
suppressfunctionality,showing how to isolate subclass logic during testing without executing unwanted parent behavior.
Motivation
Users migrating from PowerMockito or testing complex class hierarchies (such as framework base classes)
often look for a way to “suppress”
supermethod calls.MockK already supports this pattern, but it was not explicitly documented.
Adding this example improves discoverability and helps users understand how to achieve
the same behavior using
spykand explicit stubbing.Changes
README.mdParent/Childclass hierarchydemonstrating suppression via
every { ... } just runsNotes