DEV Community: Torsten Mandry

Tests Granularity

Torsten Mandry — Tue, 27 Oct 2020 07:36:18 +0000

In two previous posts (Why You Should Write Automated Tests and Anatomy of a Good Test) we discussed the benefits of automated tests and the properties of a good test. So far we were trying to avoid differentiating the tests in any way. This time we want to address one way how tests can be classified: Tests Granularity.

Anatomy of a Good Test

Torsten Mandry — Thu, 24 Sep 2020 15:54:44 +0000

In this post we will take a look at an automated test. We will show what makes a test a good one and describe desired and unwanted properties.

Why You Should Write Automated Tests

Torsten Mandry — Thu, 27 Aug 2020 09:13:58 +0000

This blog post gives an overview of the most common benefits gained by writing automated tests. It starts in a place where most of the projects we’ve seen so far are: tests are written as a last step of the development process. Then it shows additional benefits that could be gained if we all gave the tests a bit more focus and care.

Visualizing the progress of a refactoring into a Hexagonal Architecture using jQAssistant

Torsten Mandry — Mon, 24 Aug 2020 14:53:29 +0000

In my last project, we decided to refactor the inner structure of one of our services into a Hexagonal Architecture. It was clear that this was no task that could be done within a couple of days. During this long-running refactoring, we wanted to make our progress visible. Where are we now? What did we already have achieved? What do we still have to do? In my blog post, I describe the approach we took and how it helped us with our task.

Cookie-based Spring Security Session

Torsten Mandry — Tue, 11 Aug 2020 07:33:16 +0000

If you need authentication within your Spring Boot web application, the natural choice is to use
Spring Security. It's easy to use and, as long as you
stick close to the defaults, it's also quite easy to configure. But, by sticking to those defaults, you will automatically get a session that is persisted on the server-side. That's a problem if you want to run multiple instances of your application. And, additionally, it's not necessary, at least in most cases. There's another mechanism for keeping some user session state in a web application. It's called Cookie. And, instead of using it only to store a session identifier, why not let it hold the data itself. My blog post at innoq.com shows, that, with some effort, it's possible to configure Spring Security to store its session information in a cookie instead of a server-side session.