Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Mastering Software Testing with JUnit 5
  • Toc
  • feedback
Mastering Software Testing with JUnit 5

Mastering Software Testing with JUnit 5

By : Boni Garcia
4.3 (8)
close
Mastering Software Testing with JUnit 5

Mastering Software Testing with JUnit 5

4.3 (8)
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)
close

Test planning

A first step in the testing path can be the generation of a document called test plan, which is the blueprint to conduct software testing. This document describes the objective, scope, approach, focus, and distribution of the testing efforts. The process of preparing such document is a useful way to think about the needs to verify of a software system. Again, this document is especially useful when the size of the SUT and the involved team is large, due to the fact that the separation of work in different roles makes the communication a potential deterrent for the success of the project.

A way to create a test plan is to follow the IEEE 829 Standard for Test Documentation. Although this standard might be too much formal for the most of software projects, it might be worth to review the guidelines proposed in this standard, and use the parts needed (if any) in our...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete