gs-spring-boot VS AssertJ

You're welcome. You can do this fairly easily with straight java SE, but once you've done that take look at what Spring has to offer, in particular Spring Boot. Inversion of Control and Dependency Injection are super powerful!

You can try the official documentation on https://spring.io/guides/gs/spring-boot/ There are courses as well. Also you can check out https://www.baeldung.com/spring-boot

Spring does have a broilerplate "get it up and running" project. Go to start.sprint.io , configure whichever stuff you will need, download the project, import it in your IntelliJ, read and implement https://spring.io/guides/gs/spring-boot/ , then run it.

Soring's own guides are pretty good to be honest. https://spring.io/guides/gs/spring-boot/

Not necessarily a book recommendation but I’m a strong believer in actually implementing a project to learn about the tech stack. Spring has a great tutorial: https://spring.io/guides/gs/spring-boot/

Their docs are pretty complete. Here is an example with start to finish: https://spring.io/guides/gs/spring-boot/ It says you only need 15min and some libs.

Spring has a guide.

i use java with spring boot (link), also look up "MVC web development", i use thymeleaf in the html as part of the MVC approach. (i use maven to manage the packages.)

Maybe not the feedback you want, but would you consider developing something that looks like plain old (and frankly beautiful) AssertJ?

AssertJ - fluent assertions

AssertJ https://github.com/assertj/assertj

Truth or AssertJ for easier assertions in tests with better exceptions

While we are at it: AssertJ is very powerful for writing assertions.

In OO you can make beautiful DSLs that allow really declarative use within that domain, e.g. test assertions in AssertJ, but everybody in the OO world is sensible enough to not try and claim OO as such being declarative. I guess they don't feel a need to try to prove the superiority of the paradigm.

AssertJ comes with a variety of assertions that can be chained together and are specific to the type of your "actual" variable.

At any rate it comes from a library called assertj.

While Hamcrest add some fluentidity to unit tests ä, I prefer the fluent assertions of AssertJ.