The current codebase lacks automated tests, which makes it prone to regressions and hard to maintain.

By adding JUnit test classes for the mentioned classes, we can ensure that the code functions as expected and catch any potential issues early in development.

I have created separate JUnit test classes for each of the classes to thoroughly test their functionality. Each test class contains test cases for various scenarios, including edge cases and boundary conditions. This approach ensures comprehensive coverage of the codebase.

Additionally, I have followed best practices for writing unit tests, including using descriptive test method names, organizing tests into logical groups, and using assertions to validate expected outcomes. This makes the tests easy to read, understand, and maintain. This commit also includes the necessary setup for running the tests, such as adding dependencies to the build file and configuring the test runner.

Overall, this approach will lead to more robust and reliable code, making it easier to develop and maintain the application in the long run.