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.
  • Building Single-page Web Apps with Meteor
  • Toc
  • feedback
Building Single-page Web Apps with Meteor

Building Single-page Web Apps with Meteor

By : Fabian Vogelsteller
4.5 (8)
close
Building Single-page Web Apps with Meteor

Building Single-page Web Apps with Meteor

4.5 (8)
By: Fabian Vogelsteller

Overview of this book

If you are a web developer with basic knowledge of JavaScript and want to take on Web 2.0, build real-time applications, or simply want to write a complete application using only JavaScript and HTML/CSS, this is the book for you. This book is based on Meteor 1.0.
Table of Contents (15 chapters)
close
close
Preface
Preface
What this book covers
What you need for this book
Who this book is for
Conventions
Reader feedback
Customer support
Free Chapter
1
1. Getting Started with Meteor
1. Getting Started with Meteor
The full-stack framework of Meteor
Meteor's requirements
Installing Meteor
Creating our first app
Adding basic packages
Variable scopes
Meteor's folder conventions and loading order
Meteor's command-line tool
Summary
2
2. Building HTML Templates
2. Building HTML Templates
Writing templates in Meteor
Building the basic templates
Adding templates and partials
Displaying data with template helpers
Setting the data context for a template
"this" in template helpers and template callbacks
Adding events
Block helpers
Listing posts
Spacebars syntax
Summary
3
3. Storing Data and Handling Collections
3. Storing Data and Handling Collections
Meteor and databases
Setting up a collection
Adding post examples
Querying a collection
Updating a collection
Database everywhere
Differences between client and server collections
Summary
4
4. Controlling the Data Flow
4. Controlling the Data Flow
Syncing data – the current Web versus the new Web
Removing the autopublish package
Publishing data
Publishing only parts of data
Publishing specific fields
Lazy loading posts
Switching subscriptions
Some notes on data publishing
Summary
5
5. Making Our App Versatile with Routing
5. Making Our App Versatile with Routing
Adding the iron:router package
Setting up the router
Switching to a layout template
Adding another route
Moving the posts subscription to the Home route
Setting up the post route
Changing the website's title
Summary
6
6. Keeping States with Sessions
6. Keeping States with Sessions
Meteor's session object
Using sessions in template helpers
Rerunning functions reactively
Using autorun in a template
The reactive session object
Summary
7
7. Users and Permissions
7. Users and Permissions
Meteor's accounts packages
Adding the accounts packages
Adding admin functionality to our templates
Creating the template to edit posts
Creating the admin user
Creating routes for the admin
Summary
8
8. Security with the Allow and Deny Rules
8. Security with the Allow and Deny Rules
Adding a function to generate slugs
Creating a new post
Editing posts
Restricting database updates
Adding a deny rule
Adding posts using a method call
Calling the method
Summary
9
9. Advanced Reactivity
9. Advanced Reactivity
Reactive programming
Building a simple reactive object
Creating an advanced timer object
Reactive computations
Summary
10
10. Deploying Our App
10. Deploying Our App
Deploying on meteor.com
Deploying on other servers
Outlook
Summary
11
11. Building Our Own Package
11. Building Our Own Package
The structure of a package
Creating our own package
Releasing our package to the public
Summary
12
12. Testing in Meteor
chevron up
12. Testing in Meteor
Types of tests
Testing packages
Testing our meteor app
Acceptance tests
Summary
13
A. Appendix
A. Appendix
List of Meteor's command-line tool commands
The iron:router hooks
14
Index
Index

Types of tests

Tests are pieces of code that test other pieces of code or functionality of an app.

We can divide tests into four general groups:

  • Unit test: In this test, we test only a small unit of our code. This can, for example, be a function or a piece of code. Unit tests should not call other functions, write to the hard disk or database, or access the network. If such functionality is needed, one should write stubs, which are functions that return the expected value without calling the real function.
  • Integrations test: In this test, we combine multiple tests and run them in different environments to make sure that they still work. The difference in this test compared to the unit test is that we are actually running connected functionalities, such as calling the database.
  • Functional test: This can be a unit test or tests in the interface, but will only test the functionality of a feature/function without checking for side effects, such as whether or not variables were cleaned up properly...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
Start a 7-day FREE trial
End of Section 2
Next Section
bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete