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.
Java Software Testing tutorials: unit testing, open source, JUnit, Mockito, TestNG, Spring, JGiven, etc.
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?
Mockito is a popular and powerful open source Java mocking framework. In order to achieve good unit tests, you need to make use of mocks and stubs. And that’s exactly what this talk will be about: What is a mock?
Many modern applications are based on a REST API base software architecture and it is important to apply software testing verification to this code. In his article “REST API Test Automation in Java with Open Source Tools”, Vladimir Belorusets provides a good overview on how to test Java REST API with open source tools.
Although Behavior Driven Development has been existing for over 10 years, the methodology hasn’t yet been very popular in the Java world. One reason for this are the existing BDD tools for Java that are cumbersome for developers to use and require a lot of maintenance.
The microservice architecture has been growing momentum over the past few years in the Java world, but once you have started down the microservice path how do you make sure that your applications are still fully tested?