There is life in Java without Spring. Who would have thought that possible ;)
Jacek Bilski @jacek_bilski
27 Apr 2018
Ever wondered if @springframework and #testing not always should go together? Check out my new post on @INNOQ blog: innoq.com/en/blog/springless…
2
9
1
17
I can’t remember any Java framework that has had more emphasis on user code being written in a way so that you can purely unit test it.
4
4
2
26
I can only second the statement by @olivergierke here
1
2
While that may well be true, I fail to see how the post suggests something different. Everyone seems to agree using Spring in unit tests is a bad idea. What am I missing?
3
1
It starts with using Spring in a way that's know to be troublesome and that the Spring team discourages, as that style makes testing hard. It creates the impression that kind of design and testing approach is incentivized by the framework which it clearly is not.
4
8
Replying to @odrotbohm @olivergierke @bitboss
Thank you. Interesting. I note every single Spring person I know reacted the same way. I wonder, though: Does this mean it’s not being used this way? Or that the post should have stated “don’t use it this way” in its intro?

Apr 27, 2018 · 5:31 PM UTC

4
2
Replying to @stilkov @olivergierke @bitboss
Maybe I’m just observing from the outside what I typically experience from the inside when pro-GraphQL people criticize REST :)
1
3
more replies
Replying to @stilkov @bitboss
The latter. I don’t dispute that there’s a lot of code out there that looks that way but if not clearly contextual used it might create the impression that that’s the way you need to write code and things go downhill from there.
3
Replying to @stilkov @olivergierke @bitboss
As someone who's been using spring since version 0.x, I think we've gone a long way in knowing when and what parts of spring to use. I think the spring team did too.
1
Replying to @stilkov @olivergierke @bitboss
Yep exactly. Testing is not the problem addressed with the example.
1