Another month and another few books read. This time 4 new titles and one that I have already read some time ago.
So you have tests, they are well named, well structured, with given, when, then blocks and all that beautiful things, they can even fit on a screen! But do you know how and what part of your code these tests test?
Last time I wrote a bit about the importance of testing your code. This time I’ll focus more on what test has to have.
Probably every developer will agree that testing software is important, everyone expects from third-party library or application that it will work, that it is well written and thoroughly tested, even if it’s free and you do not have to pay for it. So if everyone agrees, why so many developers don’t test their code?
About one year ago, out of a sudden, I was given an opportunity for a Tech Lead position in a scrum team, and everything changed…
Another Code Europe in 2017 just took place in Warsaw, if you missed, just like I did, you can still check it out on 9th of December in Wrocław. Here are some lectures that in my opinion are worth to go and listen if you can.
Autowired annotation from Spring Framework is a wonderful thing. It makes a development of complex applications pretty easy, objects appear in your class automagically! You just splat an annotation on a field and voila! Magic happens. But it’s not a magic bullet that you should plug in everywhere.
This time it will be a really short post about books.
Some time ago I wrote about Ports and Adapters architecture, where domain logic is completely separated from infrastructure logic, like database connection, rest controllers, clients etc. It’s is great if you have external dependencies and you want to just test your domain logic without the need for low-level mocking of dependencies. But what if you have a single codebase, a monolith app? Is it useful here? The TL;DR answer is… YES. Here’s why.