15 years ago, automated tests didn’t exist in the Java ecosystem. One had to build the application and painfully test it manually by using it. I was later introduced to the practice of adding a main method to every class and putting some testing code there. That was only marginally better, as it still required to manually run the methods. Then came JUnit, the reference unit testing framework in Java which brought test execution automation.

As a consultant, I’ve done a lot of Java projects in different 'enterprise' environments. In general, the Continuous Integration stack - when there’s one, is comprised of: Github Enterprise or Atlassian Stash for source version control, Jenkins as the Continuous Integration server, sometimes but rarely Atlassian Bamboo, Maven for the build tool, JaCoCo for code coverage, or even Artifactory as the artifacts repository - once I had Nexus.