Book Image

Gradle Essentials

By : Kunal Dabir, Abhinandan Maheshwari
Book Image

Gradle Essentials

By: Kunal Dabir, Abhinandan Maheshwari

Overview of this book

Gradle is an advanced and modern build automation tool. It inherits the best elements of the past generation of build tools, but it also differs and innovates to bring terseness, elegance, simplicity, and the flexibility to build. Right from installing Gradle and writing your first build file to creating a fully-fledged multi-module project build, this book will guide you through its topics in a step-by-step fashion. You will get your hands dirty with a simple Java project built with Gradle and go on to build web applications that are run with Jetty or Tomcat. We take a unique approach towards explaining the DSL using the Gradle API, which makes the DSL more accessible and intuitive. All in all, this book is a concise guide to help you decipher the Gradle build files, covering the essential topics that are most useful in real-world projects. With every chapter, you will learn a new topic and be able to readily implement your build files.
Table of Contents (17 chapters)
Gradle Essentials
Credits
About the Authors
Acknowledgments
About the Reviewers
www.PacktPub.com
Preface
Index

Code coverage


There are so many coverage tools available for source code analysis such as EMMA, Corbatura, JaCoCo, and so on. In this section, we'll cover Gradle integration with JaCoCo to find the source code analysis.

Before we get started, we need to understand what code coverage is and why it is important in the test-driven development.

Code coverage is a metric that we can use to check how much of the source code was tested. Higher code coverage means a greater percentage of our code has been tested. Code coverage is typically done in the unit testing cycle. During code coverage, a developer must ensure that different logical paths in the source code have been tested and verified to achieve better code coverage.

Here, it is important to understand that the code coverage is not directly related to code quality. High code coverage does not guarantee that the quality code has been written. A developer must use static code analysis tools such as PMD (https://pmd.github.io/) to find the quality...