The main objective of building code tests in an application is to certify what was coded, that is, to guarantee that a given piece of code does what it should do.

It is extremely common for applications built with Spring Boot to have all their tests annotated with @SpringBootTest, but it is rare to find people who know the functionality of this annotation, when it is necessary to use it and its impact on the execution of an application’s tests.

Recently at work, we intended to use GraalVM in a new application. Looking for compatible solutions, we saw that Quarkus and Micronaut looked promising and decided to analyze them.

Recently I needed to perform some simple tests of an application that only worked on Windows and as I don’t have this environment, I decided to create a VM with Windows 10. My first idea was to use VirtualBox , however, for some reason, I couldn’t start the installer at all, always generating a random error or else the screen was like the hiss of a TV, but colorful and without sound.

Every developer, at least once, must have come across awesome lists calls. These lists try to bring together in one place projects related to a theme or libraries for which they were developed.