mockito/mockito.github.io

Mockito site project

About

Source code for Mockito site hosted at http://mockito.github.io/. Mockito source code lives at https://github.com/mockito/mockito.

Contributing to the website

The site is built with Jekyll and based on the github.com/t413/SinglePaged theme.

Clone this repository and install Jekyll:

sudo gem install github-pages

If you get permission problems on latest Mac OSx try:

sudo gem install -n /usr/local/bin/ github-pages

Then you can serve with Jekyll:

jekyll serve -w

Whenever you modify any file, the website is automatically reloaded in the browser.

mockito.github.io's Issues

HTTPS certificate expired for mockito.org

https://mockito.org/ shows an expired HTTPS certificate warning. https://site.mockito.org/ still works as expected.

Project links, groups, etc

Wiki has outdated links:

• How to contribute
• Release notes

Invalid links under "Other project links"

• Continuous integration server
• What we are working on

For Groups, consider replacing Google Groups with either a Slack workspace or Discourse forum.

Add list of maven artifacts.

Updates website to new tooling of github pages

GH Pages do not allow the current code highlighter and thus must be updated to rouge

The page build completed successfully, but returned the following warning:

You are attempting to use the 'rogue' highlighter, which is currently unsupported on GitHub Pages. Your site will use 'rouge' for highlighting instead. To suppress this warning, change the 'highlighter' value to 'rouge' in your '_config.yml' and ensure the 'pygments' key is unset. For more information, see https://help.github.com/articles/page-build-failed-config-file-error/#fixing-highlighting-errors.

For information on troubleshooting Jekyll see:

https://help.github.com/articles/troubleshooting-jekyll-builds

If you have any questions you can contact us by replying to this email.

html: missing title in head

Hi,

http://mockito.org/ has no title tag.

Update: Webpage title is shown on Chrome (text: "mockito.org"), but missing in Firefox (both latests versions).

Switch from mockito.org to mockito.github.io

We now have an external hosted site which has several issues, most notably the iframe inclusion as well as opening links (pointing you to a completely different website) and developers unable to access this external server.

Since managing and maintaining this server is a big hassle, I would propose to drop mockito.org and switch to mockito.github.io. GitHub takes care of the hosting and deploying the new website as well as updating the website is a lot easier. Do you agree @mockito/developers ?

"Contributions welcome" items alignment

I don't know if it's the desired visual alignment for those items but it looks weird on my end. Please see image below.

Out of date information

Parts of the homepage still sound like the current version is 2 and version 3 has not been released.

"What's new in Mockito 2" should be "What's new in Mockito" and it should contain description of user visible changes in the latest versions, both 2.x and 3.x. Maybe it should be merged with the release notes mentioned on the next line.

"Still on Mockito 1.x?" is probably unnecessary. It's better not to single out specific versions, but to encourage users to update once in a while to benefit from recent development.

Linking to 3 sites hosting Mockito 1.x seems excessive. All those sites have information about the recent versions of Mockito as well. It would be better to describe what those sites provide (downloads, instructions, documentation) adjust the links to the latest version and let the users look for older versions if they want (most users would probably look for the latest version).

"After releasing Mockito 2 (see what’s new) the team will continue to improve version 2.x for a short time, then focus on Mockito 3." - completely out of date! I guess if can be removed.

"see what’s new" is not new, it's another link to "What's new in Mockito 2"

"Please provide your feedback and suggestions for the scope of Mockito 3.x" - it would be better not to frame it that way. Any constructive feedback should be welcome.

"Mockito 3.x will target Java 8." - I guess it should be Mockito 4.x or perhaps "the next major release".

Install serviceworker for offline documentation access

With the new technology of a serviceworker, we can make our documentation available for offline by precaching all required package and class files. I have plenty of experience with this technology and should be able to fix this quite easily if we have a good server environment.

Remove the duplication - latest 2.x is synonymous with latest build

mockito.github.io and site.mockito.org hijacked?

The content of this repo is not what is being served up today:

$ curl -Lv mockito.github.io
* Rebuilt URL to: mockito.github.io/
*   Trying 199.27.76.133...
* Connected to mockito.github.io (199.27.76.133) port 80 (#0)
> GET / HTTP/1.1
> Host: mockito.github.io
> User-Agent: curl/7.43.0
> Accept: */*
>
< HTTP/1.1 301 Moved Permanently
< Server: GitHub.com
< Content-Type: text/html
< Location: http://site.mockito.org/
< X-GitHub-Request-Id: C71B4C1F:5D3D:2514E0E:56B25BA4
< Content-Length: 178
< Accept-Ranges: bytes
< Date: Wed, 03 Feb 2016 20:37:28 GMT
< Via: 1.1 varnish
< Age: 2404
< Connection: keep-alive
< X-Served-By: cache-jfk1024-JFK
< X-Cache: HIT
< X-Cache-Hits: 1
< X-Timer: S1454531848.930406,VS0,VE1
< Vary: Accept-Encoding
< X-Fastly-Request-ID: 2cb583cee44e923ddeaaa89c92fdae4ee292235d
<
* Ignoring the response-body
* Connection #0 to host mockito.github.io left intact
* Issue another request to this URL: 'http://site.mockito.org/'
*   Trying 199.27.76.133...
* Connected to site.mockito.org (199.27.76.133) port 80 (#1)
> GET / HTTP/1.1
> Host: site.mockito.org
> User-Agent: curl/7.43.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: GitHub.com
< Content-Type: text/html; charset=utf-8
< Last-Modified: Wed, 03 Feb 2016 17:56:57 GMT
< Access-Control-Allow-Origin: *
< Expires: Wed, 03 Feb 2016 20:07:25 GMT
< Cache-Control: max-age=600
< X-GitHub-Request-Id: C71B4C18:5592:24BEDC1:56B25BA5
< Content-Length: 788
< Accept-Ranges: bytes
< Date: Wed, 03 Feb 2016 20:37:29 GMT
< Via: 1.1 varnish
< Age: 0
< Connection: keep-alive
< X-Served-By: cache-jfk1033-JFK
< X-Cache: MISS
< X-Cache-Hits: 0
< X-Timer: S1454531849.461134,VS0,VE11
< Vary: Accept-Encoding
< X-Fastly-Request-ID: fa40c282ba4f00621bb817f20c573ff421d746d1
<
<h3 id="training-by-core-engineers">Training by core engineers</h3>

<p>Mockito core engineers, experts in the field of software quality can help you with:</p>

<ul>
  <li>getting your team up to speed with test automation with mock objects</li>
  <li>enabling and sustaining test driven development in its best form: BDD</li>
  <li>achieving maintainable, high quality tests that unlock continuous delivery</li>
  <li>securing production code quality and minimizing defects through rigorous test automation</li>
</ul>

<p>Get in touch at <a href="&#109;&#097;&#105;&#108;&#116;&#111;:&#105;&#110;&#102;&#111;&#064;&#109;&#111;&#099;&#107;&#105;&#116;&#111;&#046;&#111;&#114;&#103;">&#105;&#110;&#102;&#111;&#064;&#109;&#111;&#099;&#107;&#105;&#116;&#111;&#046;&#111;&#114;&#103;</a></p>
* Connection #1 to host site.mockito.org left intact

Updating Android Version

Currently, way to add mockito as dependency on website is of form

dependencies { testCompile "org.mockito:mockito-core:2.+" }

In new versions, testCompile is deprecated. Better to replace it with testImplementation.
Also, the latest version is 3.+

Dead link (to ReturnValues) on http://site.mockito.org/

On _posts/2000-01-15-more.md the link to ReturnValues returns an error (as ReturnValues was deprecated).

Also the link to Answer points to http://javadoc.io/page/org.mockito/mockito-core/latest/org/mockito/Mockito.html#field_summary.
Shouldn't it be http://javadoc.io/page/org.mockito/mockito-core/latest/org/mockito/Mockito.html#answer_stubs or http://javadoc.io/page/org.mockito/mockito-core/latest/org/mockito/stubbing/Answer.html ?

Thanks for the site!

Enable https

Per https://twitter.com/github/status/991366832421523456 it should now be possible to enable https on our website 🎉

Link for Contribute a pull request! Broken in firefox and Chrome

Link for Contribute broken on first page on mockito.org. User ends up at various places depending on browser.

I was going to create a pull request with a correction of the link, but could not find a page that actually contained contribution information.

Should the link exist? If so, where should it point? My suggestion would be removing it if there is no information to link to.

Update contact information

Add the new twitter account and fix emails. Apparently there are some emails on it that are incorrect.

site.mockito.org is down

Not sure where else to mention this, but https://site.mockito.org is currently down (verified from various "is it down" checkers as well).

The style of javadoc pages seem to be broken

https://javadoc.io/doc/org.mockito/mockito-core/latest/org/mockito/Mockito.html