Serge Bishyr
Serge Bishyr
@davinkevin @TimvdLippe I can confirm that the issue is reproducible on the latest master code. I can take a look at this
@TimvdLippe @mockitoguy could you please consult me? The issue here is that we are creating a new mock before each test method even if the test instance is the same...
Do you mean not to create a new mock for the same instance and reuse the same mocks without resetting it? Wouldn't it differ from TestNG implementation? I can see...
@TimvdLippe yes, but for JUnit shouldn't we as well make sure that the mocking in test A does not infect the mocking in test B? If I understand correctly, if...
@TimvdLippe with repeated test do you mean the test annotated with `@RepeatedTest`? I cannot see how this case makes the difference. Still, maybe I am missing some important point, but...
Besides that, I guess that it is possible to know in `MockitoExtension` if it the method is annotated with `@RepeatedTest` :)
@mockitoguy in the `MockitoExtension` class there is a method `retrieveAnnotationFromTestClasses` which can be refactored to generic to return Optional of the desired annotation. For now, it's hardcoded to return `@MockitoSettings`...
The same way we can find out whether the test class is annotated with `@TestInstance(TestInstance.Lifecycle.PER_CLASS)`
@sbrannen thanx, didn't know that 👍
Same for me with `kubectl`, but other completions work fine. Also adding the following doesn't work: ``` autoload -U +X compinit && compinit autoload -U +X bashcompinit && bashcompinit ```...