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
Enterprise Application Development with Ext JS and Spring

You're reading from   Enterprise Application Development with Ext JS and Spring Designed for intermediate developers, this superb tutorial will lead you step by step through the process of developing enterprise web applications combining two leading-edge frameworks. Take a big leap forward in easy stages.

Arrow left icon
Product type Paperback
Published in Dec 2013
Publisher Packt
ISBN-13 9781783285457
Length 446 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Gerald Gierer Gerald Gierer
Author Profile Icon Gerald Gierer
Gerald Gierer
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface 1. Preparing Your Development Environment FREE CHAPTER 2. The Task Time Tracker Database 3. Reverse Engineering the Domain Layer with JPA 4. Data Access Made Easy 5. Testing the DAO Layer with Spring and JUnit 6. Back to Business – The Service Layer 7. The Web Request Handling Layer 8. Running 3T on GlassFish 9. Getting Started with Ext JS 4 10. Logging On and Maintaining Users 11. Building the Task Log User Interface 12. 3T Administration Made Easy 13. Moving Your Application to Production A. Introducing Spring Data JPA
Index

Unit testing overview

Unit testing is a strategy for testing discrete units of source code. From a programmer's perspective, a unit is the smallest testable part of an application. A unit of source code is usually defined as a public method that is callable within the application and has a specific purpose. Unit testing of the DAO layer will ensure that each public method has at least one appropriate test case. In practice, we will need many more test cases than just a single one for each public method. For example, every DAO find(ID) method requires at least two test cases: one with an outcome returning a valid found object and one with an outcome that does not find a valid object. As a result, for every line of code written, developers often need several lines of test code.

Unit testing is an art form that takes time to master. Our goal is to establish a set of tests that cover as many scenarios as possible. This is inherently opposite to what we are trying to achieve as developers...

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