Book Image

Modular Programming in Java 9

By : Koushik Srinivas Kothagal
Book Image

Modular Programming in Java 9

By: Koushik Srinivas Kothagal

Overview of this book

The Java 9 module system is an important addition to the language that affects the way we design, write, and organize code and libraries in Java. It provides a new way to achieve maintainable code by the encapsulation of Java types, as well as a way to write better libraries that have clear interfaces. Effectively using the module system requires an understanding of how modules work and what the best practices of creating modules are. This book will give you step-by-step instructions to create new modules as well as migrate code from earlier versions of Java to the Java 9 module system. You'll be working on a fully modular sample application and add features to it as you learn about Java modules. You'll learn how to create module definitions, setup inter-module dependencies, and use the built-in modules from the modular JDK. You will also learn about module resolution and how to use jlink to generate custom runtime images. We will end our journey by taking a look at the road ahead. You will learn some powerful best practices that will help you as you start building modular applications. You will also learn how to upgrade an existing Java 8 codebase to Java 9, handle issues with libraries, and how to test Java 9 applications.
Table of Contents (19 chapters)
Title Page
Credits
About the Author
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface

Unit testing modules with Java 9


The readability and accessibility constraints pose new and interesting problems when it comes to testing in Java 9. Let's look back at the way we've always been unit testing code in Java. Here are two common practices:

  • The unit test code typically resides in a separate source folder that is added to the classpath. This is to separate the test code from the actual application code and to also make it easy to exclude the test folder when building an application for deployment.
  • The unit test classes typically share the same package as the class under test. This is to make sure the test classes can access the package-private members of the classes under test, even though they are in a completely different location.

These two design decisions work well when classes are in the classpath, because we know that the physical location of the classes in the classpath doesn't matter. However, all that is changing with Java 9! Here's how:

  • In Java 9, the test code could face...