-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Improve documentation #93
Comments
So you'd want this item list in the main README.md ? Or maybe something else in a started guide in the wiki ? |
Docs are not great. Do you want to contribute some changes? :) Down the road, I'd like to have Mockito 'site', static html would be enough. |
I'll see to suggest a change to the README.md. |
The examples could be rewritten to include some of the main features using the prefered way (e.g., I'd use BDD and annotations). |
Another thing that should be done is split http://mockito.github.io/mockito/docs/current/org/mockito/Mockito.html to have the main content there in a new page (ex: |
@bric3 Yes that could help a bit. |
However I kind of like the current Mockito javadoc as is. |
@bric3 The issue is that it's the main class with methods etc. and it's mixed with a good document giving the overview of all Mockito features and classes. It's like an index mixed with a class documentation. It may be also part of the reason why going to a field's link doesn't work properly. |
Hey Werner. Thanks a lot for looking into improving our documentation. I'm allocating my time other parts of the system (release automation) but documentation will be next :) |
I've submitted a pull request for at least the home page. Still missing:
|
Not gonna happen. It is our documentation entry point.
There's always the wiki for that :) Closing as the PR has been merge, thx again for taking care of the doc. |
Documentation is missing many important features (or at least should introduce them in the main readme even they are somewhere described if you find):
-> http://mockito.github.io/mockito/docs/current/org/mockito/Mockito.html
@Spy
: Call the real object but record what has been called-> http://mockito.github.io/mockito/docs/current/org/mockito/Mockito.html#spy
@InjectMocks
: Used as a kind of simple dependency injection.-> http://mockito.github.io/mockito/docs/current/org/mockito/InjectMocks.html
@Captor
: Used to capture what arguments where called.-> http://mockito.github.io/mockito/docs/current/org/mockito/Captor.html
any()
used toverify()
something was called with any kind of argument.-> http://mockito.github.io/mockito/docs/current/org/mockito/Matchers.html#any()
For most I'd include the relevant
import
as well. I'd also put an exampleverify()
withany()
before even one verifying a specific object was called.The text was updated successfully, but these errors were encountered: