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.
OutputCapture reset method is package-private
See original GitHub issueHello, I’m currently trying to utilize OutputCapture in my unit testing to test logging level. And I face issue that I’m not able to reset OutputCapture, but according this pull request this functionality should be implemented. My spring-boot version is 2.7.4.
Probably, I can change fixture of test every time by using @TestInstance(TestInstance.Lifecycle.PER_METHOD), but I suppose that is not the best solution.
I suppose, adding any functionality to check logging level would be a very good contributing as well.
Issue Analytics
- State:
- Created 10 months ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
If you’re using Java 11 or later,
java.lang.String.lines()is another option for getting each line from the captured output.systemCapturesholds a collection ofSystemCaptureinstance, but these don’t necessarily relate to lines. They are rather a block of captured bytes (which may or may not be a complete line). I think we should keep this internal to the class.If you want to to do per line assertions you can do
.spit(...)onCapturedOutput.getAll()