Selenium is a widely used open source framework for end-to-end web testing nowadays. JUnit 5 is the latest version of this popular Java open source unit testing framework and implements a brand-new programming and extension model named Jupiter. This talk presents Selenium-Jupiter. This is an open-source JUnit 5 extension that provides seamless integration with Selenium.
The TestContainers library facilitates simple start up of a service dependencies, i.e. Postgres, Redis in throwaway Docker containers. This open source library works over Docker API and has a list of features which significantly improve a software developer experience.
Junit 5 is a big step for the world of unit testing for Android apps. This is a new very flexible open source testing framework, based on many years of experiences with Junit 4. At the sporttotal company, we use Junit 5 for our Android unit tests and it changed the way we write our tests. Hard for us to imagine living without features like @Nested. Other features we ignored as those are more leaning towards Java and are solved already by Kotlin or other Kotlin libraries. And some features are even breaking changes.
Spock was a game changer for all the Java software developers struggling with unit testing in JUnit 4. Compact syntax, parameterized tests or flexibility to mention just a few advantages. Over 10 years after JUnit 4.0, the brand new, written from scratch, Java 8 optimized JUnit 5 has been released. Is it still worth to write tests in Spock?
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.
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?