Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Advanced Search Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying MASTERING UNIT TESTING USING MOCKITO AND JUNIT
  • Table Of Contents Toc
  • Feedback & Rating feedback
MASTERING UNIT TESTING USING MOCKITO AND JUNIT

MASTERING UNIT TESTING USING MOCKITO AND JUNIT

By : Acharya
4 (11)
Buy this Book
close
close
MASTERING UNIT TESTING USING MOCKITO AND JUNIT

MASTERING UNIT TESTING USING MOCKITO AND JUNIT

4 (11)
By: Acharya
Buy this Book

Overview of this book

A practical and easy-to-follow, yet comprehensive, guide to learning advanced JUnit testing. Each topic is explained and placed in context, and for the more inquisitive, there are more details of the concepts used. This book is for you if you are a developer with some experience in Java application development as well as a basic knowledge of JUnit testing. But for those whose skill set is void of any prior experience with JUnit testing, the book also covers basic fundamentals to get you acquainted with the concepts before putting them into practise.
Table of Contents (12 chapters)
close
close
close
Preface
Icon
Preface
Icon
What this book covers
Icon
What you need for this book
Icon
Who this book is for
Icon
Conventions
Icon
Reader feedback
Icon
Customer support
Lock Free Chapter
1
1. JUnit 4 – a Total Recall
Icon
1. JUnit 4 – a Total Recall
Icon
Defining unit testing
Icon
Working with JUnit 4
Icon
Working with JUnit 4++
Icon
Summary
2
2. Automating JUnit Tests
Icon
2. Automating JUnit Tests
Icon
Continuous Integration
Icon
Jenkins
Icon
Summary
3
3. Test Doubles
Icon
3. Test Doubles
Icon
Dummy
Icon
Stub
Icon
Fake
Icon
Mock
Icon
Spy
Icon
Summary
4
4. Progressive Mockito
Icon
4. Progressive Mockito
Icon
Working with Mockito
Icon
Drinking Mockito
Icon
Summary
5
5. Exploring Code Coverage
Icon
5. Exploring Code Coverage
Icon
Understanding code coverage
Icon
Configuring the Eclipse plugin
Icon
Measuring coverage using Gradle
Icon
Working with the Maven Cobertura plugin
Icon
Running the Cobertura Ant task
Icon
Summary
6
6. Revealing Code Quality
Icon
6. Revealing Code Quality
Icon
Understanding the static code analysis
Icon
Working with the Checkstyle plugin
Icon
Exploring the FindBugs plugin
Icon
Working with the PMD plugin
Icon
Monitoring code quality with SonarQube
Icon
Getting familiar with false positives
Icon
Summary
7
7. Unit Testing the Web Tier
Icon
7. Unit Testing the Web Tier
Icon
Unit testing servlets
Icon
Playing with Spring MVC
Icon
Summary
8
8. Playing with Data
Icon
8. Playing with Data
Icon
Separating concerns
Icon
Unit testing the persistence logic
Icon
Simplifying persistence with Spring
Icon
Verifying the system integrity
Icon
Writing integration tests with Spring
Icon
Summary
9
9. Solving Test Puzzles
Icon
9. Solving Test Puzzles
Icon
Working with the legacy code
Icon
Designing for testability
Icon
Working with greenfield code
Icon
Summary
10
10. Best Practices
chevron up
Icon
10. Best Practices
Icon
Writing meaningful tests
Icon
Automating JUnit tests
Icon
Configuring tests
Icon
Working with assertions
Icon
Handling exceptions
Icon
Working with test smells
Icon
Summary
11
Index
Icon
Index

Working with test smells

Code smell is a technical debt or symptom that indicates a deeper problem. Smells are not bugs, or they don't fail tests. Instead, they indicate a problem in design or code such that a rigid code cannot be enhanced or can create a maintenance issue. This section covers the test smells that should be refactored for maintenance and readability. The following topics are covered:

  • Test code duplication

  • Conditions in test code

  • Test logic in the production code

  • Over engineering

Refactoring duplicates

Code duplication is the simplest code smell. It creates maintainability problems. The same code is written in many places; if any bug is found, then you need to modify all other places. This subsection elaborates on the duplicate code in test cases.

Suppose you are designing a hospital management system and writing a test for checking a patient in. The following objects are needed for the patient check-in process: a person, a guarantor, reason for hospitalization, the attending physician...

Visually different images
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
MASTERING UNIT TESTING USING MOCKITO AND JUNIT
End of Section 10
Next Section
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful
Order Page Read Now

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon