-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Added missing Javadoc and few other tidy-ups #842
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
mockitoguy
commented
Dec 23, 2016
- No API / no behavior changes.
- Publicly visible changes:
- Added missing Javadoc and updated an existing one for MockitoException and MockitoAssertionError classes
- Remaining changes, refactoring:
- Rename job for consistency
- Removed some unnecessary code
- Made the tests more stable
It's already included in the interface hierarchy
'Impl' postfix in the interface name is very awkward
Also tweaked existing javadoc
This fixes recently introduced flakiness of the build.
Current coverage is 86.57% (diff: 100%)
|
@@ -17,7 +17,7 @@ public void shouldCreateRunnerInstance() throws Throwable { | |||
//given | |||
RunnerProvider provider = new RunnerProvider(); | |||
//when | |||
RunnerImpl runner = provider.newInstance("org.mockito.internal.runners.SilentJUnitRunner", this.getClass(), null); | |||
InternalRunner runner = provider.newInstance("org.mockito.internal.runners.DefaultInternalRunner", this.getClass(), null); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the runner is in the same package as the factory I don't see why it should be a String ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point! Code updated!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, about the JUnit on the classpath, but will the RunnerFactory
be used at all then ? The only reasonable use is in the Silent
runner class which itself extends the JUnit Runner
class.
For maintainability