Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
The Java Workshop

You're reading from   The Java Workshop Learn object-oriented programming and kickstart your career in software development

Arrow left icon
Product type Paperback
Published in Oct 2019
Publisher Packt
ISBN-13 9781838986698
Length 606 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (3):
Arrow left icon
Eric Foster-Johnson Eric Foster-Johnson
Author Profile Icon Eric Foster-Johnson
Eric Foster-Johnson
Andreas Göransson Andreas Göransson
Author Profile Icon Andreas Göransson
Andreas Göransson
David Cuartielles David Cuartielles
Author Profile Icon David Cuartielles
David Cuartielles
Arrow right icon
View More author details
Toc

Table of Contents (20) Chapters Close

Preface 1. Getting Started FREE CHAPTER 2. Learning the Basics 3. Object-Oriented Programming 4. Collections, Lists and Java's Built-In APIs 5. Exceptions 6. Libraries, Packages, and Modules 7. Databases and JDBC 8. Sockets, Files, and Streams 9. Working with HTTP 10. Encryption 11. Processes 12. Regular Expressions 13. Functional Programming with Lambda Expressions 14. Recursion 15. Processing Data with Streams 16. Predicates and Other Functional Interfaces 17. Reactive Programming with Java Flow 18. Unit Testing Appendix

Getting Started with Unit Tests

A unit test tests one unit of code. In Java terms, this usually means that a unit test tests a single Java class. The test should run quickly, so you know whether there are any problems as soon as possible.

A unit test is a separate Java class designed just for testing. You should write separate test methods for each part of the original class you want to test. Typically, the more fine-grained the test, the better.

Sometimes, due to necessity, a unit test will test more than one class. That's OK and not something to worry about. In general, though, you want to concentrate on writing separate tests for each class in your Java application.

Note

Writing your Java classes so that they are easy to test will improve your code. You'll have better code organization, clearer code, and better quality as a result.

Integration tests, on the other hand, test a part of the entire system, including external dependencies. For example, a unit...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image