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
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Node Web Development - Second Edition

You're reading from   Node Web Development - Second Edition JavaScript is no longer just for browsers and this exciting introduction to Node.js will show you how to build data-intensive applications that run in real time. Benefit from an easy, step-by-step approach that really works.

Arrow left icon
Product type Paperback
Published in Jul 2013
Publisher
ISBN-13 9781782163305
Length 248 pages
Edition Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
David Herron David Herron
Author Profile Icon David Herron
David Herron
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Node Web Development Second Edition
Credits
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface
1. About Node FREE CHAPTER 2. Setting up Node 3. Node Modules 4. HTTP Servers and Clients – A Web Application's First Steps 5. Implementing a Simple Express Application 6. Data Storage and Retrieval 7. Multiuser Authorization, Deployment, Scaling, and Hosting 8. Dynamic Interaction between the Client and Server Application 9. Unit Testing Index

Chapter 9. Unit Testing

Unit testing has become a primary part of good software development practices. It is a method by which individual units of source code are tested to ensure proper functioning. Each unit is theoretically the smallest testable part of the application. For Node, you could consider each module as a unit to test individually.

In unit testing, each unit is tested separately, isolating the unit from other parts of the application. Common techniques are to use mock objects, and other methods, to fake out the dependencies, so that application units can be reliably tested in isolation. We will be focusing on that testing model in this chapter.

Functional testing doesn't try to test individual components of the system, but instead tests the whole system. Generally speaking, unit testing is performed by the software development team as they write the code, and functional testing is performed by the QA or Quality Engineering (QE) team. Both testing models are needed to fully certify...

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