The previous post of my new Spring MVC Test tutorial taught us that we should configure the system under test by using the standalone configuration when we are writing unit tests for Spring MVC controllers. In this blog post, we will put theory into
I just published a free sample lesson of my Test With Spring course. After we have finished this lesson, we: Understand how we can remove duplicate code from our test suite. Can configure the system under test by using the standalone configuration
Before we can write unit tests for Spring MVC controllers, we have to configure the system under test (aka the Spring MVC Test framework). Unfortunately, before we can write the code that configures the Spring MVC Test framework, we have to be able
I have written quite a bit about the TestProject framework, and my TestProject tutorial provides us the technical skills which we need when we write tests for our web applications. This is a good start, but it’s not enough. Before we can truly
We can remove duplicate code from our TestProject test suite by using web actions. Even though web actions make our life easier, they have a access to the entire DOM, and this can make our test code more complicated than it could be. This blog post
This blog post is the first part of my new Spring MVC Test tutorial. This tutorial helps you to write unit and integration tests for Spring MVC controllers with JUnit 5. However, before we can get to the good stuff, we have to understand the basics.