Running automated tests is a good thing for software quality assurance. Now you have to understand the results of the current test run. You could also be interested to see how your tests results evolve over time. To achieve these goals, you need a tool to produce meaningful tests reports and there are some open source tools to help you do this.
Java Software Testing tutorials: unit testing, open source, JUnit, Mockito, TestNG, Spring, JGiven, etc.
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?
Spock is a Groovy-based open source testing and specification framework for Java and Groovy applications that makes writing tests fun again. We can write beautiful and highly expressive tests for Java applications because of its domain-specific language (DSL) and all the power that Groovy provides us.
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.