Add tests for ball logic in image resolver page

[Okhan-coder]

This merge has 3 unit tests covering Ball Logic, First Test sees if the default 32x32 image logic is correct. The second is just a regular ball, and 3rd is an empty test case. I also Updated Mockito so it works with Final classes. Still need to cover non-ball image requests but will handle that at a later time. #114

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue

[MarkEWaite]

Thanks for the pull request @Okhan-coder . In future pull requests, please create a branch for the changes instead of submitting it from your master branch. The first item in the submitter checklist says:

• [ ] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!

When you submit a pull request from your own master branch, you make your own development experience more complicated and you make it a little more complicated for the plugin maintainer.

[Okhan-coder]

Apologies I will pay attention to that in the future thank you!

[MarkEWaite]

I started some experiments to create comparable tests without using mocks and it seemed to be working well. I ran out of time to complete those comparable tests, but if you're interested in my "work in progress" I could push them to this pull request (on your branch). Would that be OK or would you rather I push my prototypes to branch in my own repository that you can then use for comparison without it disrupting your branch?

In case you're interested in the experiments I was doing to try to use the objects directly rather than mocking, see https://github.com/MarkEWaite/embeddable-build-status-plugin/commits/Okhan-coder/master

[Okhan-coder]

I started some experiments to create comparable tests without using mocks and it seemed to be working well. I ran out of time to complete those comparable tests, but if you're interested in my "work in progress" I could push them to this pull request (on your branch). Would that be OK or would you rather I push my prototypes to branch in my own repository that you can then use for comparison without it disrupting your branch?

In case you're interested in the experiments I was doing to try to use the objects directly rather than mocking, see https://github.com/MarkEWaite/embeddable-build-status-plugin/commits/Okhan-coder/master

Pushing them to this pull request would be great thanks!

[Okhan-coder]

Hello Mark, To make these tests work without mocks I had to make an extension of ImageResolver in the test. The reason for this is Color. getimageof () used the Stapler class which always returned a null pointer exception. I was unsure how to stop this from happening without mocks. If you have any solutions that don't include extensions to this let me know I can change the code.

[MarkEWaite]

Thanks. Sorry for the long delay on my feedback.

[MarkEWaite]

The tests that I added would benefit from more work, but that's only peripherally part of this pull request. The test you added looks good to me.