Stefano Cordio
Stefano Cordio
Sure and thanks, @nith2001. Please just consider that we are short on capacity and this topic is a corner case, so it may take some time before we can provide...
I'd go with: ``` Warning: this will consume the first byte of the {@code InputStream} if the underlying implementation does not support {@link InputStream#markSupported() marking}. ``` About the code snippet,...
@jessicant yes, I had roughly this in mind. Maybe an additional parameter is needed for the `readLimit` of `mark`, probably 1 is not enough in case of some assertions like...
No worries, @jessicant, and thank you both for spending time on it! Feel free to raise a draft PR and we could brainstorm together over there about the next steps.
@raphw is there any example I could look at in Byte Buddy or Mockito about the build plugin?
Unfortunately, we haven't had enough capacity to look into it so far. I'll add it to the next release scope for a first analysis.
@sormuras has a [nice blog post](https://sormuras.github.io/blog/2018-09-11-testing-in-the-modular-world.html) on this subject.
Yes, the library is in the classpath: if I call one of the methods without mocking, it fails in the static initialization block with a missing native library error, as...
No, they are not the same. The successful one: * Is also public, top level and non-final * Has also default constructor that is private and does nothing * Has...
Mockito has no way to catch multiple failures thrown by the `Consumer` of `assertArg`. If such behavior is desired, the writer of the `Consumer` should take care of it, e.g.:...