https://advancedweb.hu/2015/09/17/eclipse_tests_with_moreunit/

Ctrl+j -> edit test class

Ctrl+u -> edit test method

Ctrl+r -> run test

Don’t Test Blindly

• https://zeroturnaround.com/rebellabs/dont-test-blindly-the-right-methods-for-unit-testing-your-java-apps/
• https://zeroturnaround.com/rebellabs/why-your-next-cloud-app-will-probably-suck-without-unit-testing/

In this case you should prioritize things a bit and just write tests for the following:

• Core code that is accessed by a lot of other modules
• Code that seems to gather a lot of bugs
• Code that changes by multiple different developers (often to accommodate new requirements)

MEMO

• https://zeroturnaround.com/rebellabs/rebel-labs-report-go-away-bugs-keeping-your-code-safe-with-junit-testng-and-mockito/