Java Software Testing tutorials: unit testing, open source, JUnit, Mockito, TestNG, Spring, JGiven, etc.
Testing and validating REST services in Java is harder than in dynamic languages such as Ruby and Groovy. REST Assured is an open source software testing tool that brings the simplicity of using these languages into the Java domain.
This tutorial presents how to do Test-Driven Development (TDD) for a Spring Boot application and how some of the latest Spring Boot annotations and utilities make that easy. Ever wonder how to test a hard problem like caching or write an integration test without making an external API call? Or come across a situation where testing something was so hard that it never got tested?
It is not easy to write good automated tests as it involves to create and maintain a stable testing environment and configure the right tools. In this free less extracted from his “Test With Spring” course, Petri Kainulainen explains how to run integration tests With Maven, Spock edition.
The possibilities to write parametrized tests have changed and improved a lot with the release of JUnit 5, the open source unit testing tool for Java. In his blog post “Using JUnit 5 Parameterized Tests, Argument Sources and Converters”, Micha Kops provides an overview covers all new types of parameter sources for JUnit 5 tests as well as the new conversion API for test arguments.
JUnit 5 is the next generation of JUnit. The goal is to create an up-to-date foundation for developer-side testing on the JVM. This includes focusing on Java 8 and above, as well as enabling many different styles of testing.
JUnit 5 is the next generation of JUnit. The goal of this upcoming version is to create an up-to-date foundation for developer-side testing on the JVM. The evolution includes focusing on Java 8 and above, as well as enabling many different styles of testing. In his article, Nicolai Parlog explains how you should write tests with JUnit 5.
Testing has been part of the software delivery lifecycle since… forever. Now, Agile methodologies make testing part of everyone’s responsibilities. But despite this, despite big steps forward with TDD, BDD, and other approaches which bring automated testing to the forefront of the development process, many developers still behave as if testing is a second class citizen. What can you do to help developers a) write tests b) write meaningful tests and c) write readable tests?