Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Provide a Kofu equivalent of @MockkBean
See original GitHub issueCollaborate with @jnizet on a Kofu variant of @MockkBean from https://github.com/Ninja-Squad/springmockk (see https://github.com/spring-projects/spring-boot/issues/15749 for the context).
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (1 by maintainers)
Top Results From Across the Web
Provide a Kofu equivalent of @MockkBean · Issue #151 - GitHub
I am not sure this is something we want to support, the functional variant is not a strict equivalent of the annotation based...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I am not convinced there is a need for that since the customizing capabilities bring by #44 are pretty powerful so I prefer to close this issue for now, feel free to reopen if there is some concrete PR or proposal.
The customize function work well but I think it’s could be more easier to use. A solution could be to mockk an entire configuration block like :
I don’t know if it’s possible to have a list of all the beans create by a configuration and mock them ?