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

Testing a model


Let's start our journey of using the Notes application to explore testing with the data models. Because this is unit testing, the models should be tested separately from the rest of the Notes application.

That would, in the case of the models, mean creating a mock database object. To test a data model and not mock out the database means that for the test to run, the database server must be running, making it a dependency of the test. However, in this case it would mean creating a fake Sequelize library, which does not look like a productive use of our time. One can also argue that testing a data model really means you're testing the interaction between your code and the database, and that mocking out the database means not testing that interaction.

Therefore we are going to skip creating a mock database module, and test the model against a real database server. Instead of running the test against the live production database, it should be run against a test database that contains...

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