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.

Related Content you might be interested in

Current Title:

Small book image
Mastering Software Testing with JUnit 5
Boni Garcia
Oct, 2017 | 350 pages
Small book image
Test-Driven Java Development
Alex Garcia | Viktor Farcic
Mar, 2018 | 324 pages
Small book image
Building Web Apps with Spring 5 and Angular 4
Ajitesh Kumar Shukla
Aug, 2017 | 370 pages
Small book image
Learning Android Application Testing
Paul Blundell | Eduardo Diego Torres Milano
Mar, 2015 | 274 pages
Table of Contents (8 chapters)
Preface
Preface
What this book covers
What you need for this book
Who this book is for
Conventions
Reader feedback
Customer support
Free Chapter
1
Retrospective On Software Quality And Java Testing
Retrospective On Software Quality And Java Testing
Software quality
Software testing
Testing frameworks for the JVM
Summary
2
What’s New In JUnit 5
What’s New In JUnit 5
Road to JUnit 5
JUnit 5 architecture
Running tests in JUnit 5
The extension model of JUnit 5
Summary
3
JUnit 5 Standard Tests
JUnit 5 Standard Tests
Test lifecycle
Assertions
Tagging and filtering tests
Conditional test execution
Nested tests
Repeated tests
Migration from JUnit 4 to JUnit 5
Summary
4
Simplifying Testing With Advanced JUnit Features
Simplifying Testing With Advanced JUnit Features
Dependency injection
Dynamic tests
Test interfaces
Test templates
Parameterized tests
Java 9
Beyond JUnit 5.0
Summary
5
Integration Of JUnit 5 With External Frameworks
Integration Of JUnit 5 With External Frameworks
Mockito
Spring
Selenium
Cucumber
Docker
Android
REST
Summary
6
From Requirements To Test Cases
From Requirements To Test Cases
The importance of requirements
Test planning
Test design
Software testing principles
Test anti-patterns
Summary
7
Testing Management
Testing Management
Software development processes
Continuous Integration
Test reporting
Defect-tracking systems
Static analysis
Putting all pieces together
Summary

Software development processes

In software engineering, the software development process (also known as the software development life cycle) is the name given to the workflow for the activities, actions, and tasks required to create software systems. As introduced in Chapter 6, From Requirements to Test Cases, the usual phases in any software development process are:

  • Definition of what: Requirements elicitation, analysis and use case modeling.
  • Definition of how: The system architecture and modeling of structural and behavioral diagrams.
  • The actual software development (coding).
  • The set of activities that makes the software available for use (release, installation, activation, and so on).

The timing in which tests are designed and implemented in the overall software development process results in different test methodologies, namely (see diagram after the list):

  • Behavior-Driven...
Previous Section
End of Section 2
Next Section