Book Image

Mastering Software Testing with JUnit 5

By : Boni Garcia
Book Image

Mastering Software Testing with JUnit 5

By: Boni Garcia

Overview of this book

When building an application it is of utmost importance to have clean code, a productive environment and efficient systems in place. Having automated unit testing in place helps developers to achieve these goals. The JUnit testing framework is a popular choice among Java developers and has recently released a major version update with JUnit 5. This book shows you how to make use of the power of JUnit 5 to write better software. The book begins with an introduction to software quality and software testing. After that, you will see an in-depth analysis of all the features of Jupiter, the new programming and extension model provided by JUnit 5. You will learn how to integrate JUnit 5 with other frameworks such as Mockito, Spring, Selenium, Cucumber, and Docker. After the technical features of JUnit 5, the final part of this book will train you for the daily work of a software tester. You will learn best practices for writing meaningful tests. Finally, you will learn how software testing fits into the overall software development process, and sits alongside continuous integration, defect tracking, and test reporting.
Table of Contents (8 chapters)

Test reporting

From its initial versions, the JUnit testing framework introduced an XML file format to report the execution of test suites. Over the years, this XML format has become a de facto standard for reporting test results, broadly adopted in the xUnit family.

These XML can be processed by different programs to display the results in a human-friendly format. This is for example what build servers do. For example, Jenkins implements a tool called JUnitResultArchiver, which parses to HTML the XML files resulting from the test execution of a job.

Despite the fact that this XML format has become pervasive, there is no universal formal definition for it. JUnit test executors (for example, Maven, Gradle, and so on) usually use its own XSD (XML Schema Definition). For instance, the structure of this XML report in Maven (http://maven.apache.org/surefire/maven-surefire-plugin/)...