20 Spring Security testing

The legend says that writing unit and integration tests started with a short verse:

“99 little bugs in the code,

99 little bugs.

Track one down, patch it around,

There’s 113 little bugs in the code.”

--Anonymous

With time, software became more complex, and teams became larger. Knowing all the functionalities implemented over time by others became impossible. Developers needed a way to make sure they didn’t break existing functionalities while correcting bugs or implementing new features.

While developing applications, we continuously write tests to validate that the functionalities we implement work as desired. The main reason why we write unit and integration tests is to make sure we don’t break existing functionalities when changing code for fixing a bug or for implementing new features. This is also called regression testing.

20.1 Using mock users for tests

20.2 Testing with users from a UserDetailsService

20.3 Using custom Authentication objects for testing

20.4 Testing method security

20.5 Testing authentication

20.6 Testing CSRF configurations

20.7 Testing CORS configurations

20.8 Testing reactive Spring Security implementations

Summary