@dave08 I really like your idea of testing for behavior, not frameworks. I will definitely need to take a step back tonight on testing so I can think of a more objective way of testing APIs without stumbling over ridiculous issues like these

Also, I liked this article https://blog.iterate.no/2012/06/20/programming-like-kent-beck/, a bit old but I got from it that you don't need to test everything... but not everything needs a unit test in the beginning... you need input vs. Output, until things get too complex...

I recently read an interesting article on dynamic vs. statically typed programming, where the argument for dynamic was that if you tested everything, why bother adhering to compiler checks: I find it irksome that spring would have a similar philosophy if it is surrounding java development in the first place 😕

"I find it irksome that spring would have a similar philosophy... " at its worst, Spring gets you 100% of the error modes of dynamic types in exchange for 5% of their expressiveness

@bissell If you have any sources you refer to for spring testing, I would really appreciate it! This is a project I'm doing on my own, so unfortunately I don't have anyone to show me creative ways to work with Spring