Chapter 1, Setting Up a Test Infrastructure, starts with the basics of how to set up your test application code and obtain the test libraries that we will use throughout this book. We create a basic test infrastructure, write the first tests, and review the test report results.

Chapter 2, Creating a Backbone.js Application Test Plan, begins with a refresher of Backbone.js fundamentals, introduces a sample web application for the book, and discusses a wide range of relevant testing and planning concepts. We conclude by writing and running our first Backbone.js application tests.

Chapter 3, Test Assertions, Specs, and Suites, covers the basics of writing Backbone.js test suites and specs with Mocha and test assertions with Chai.

Chapter 4, Test Spies, introduces the Sinon.JS test double library and how to spy on application method behaviors in Backbone.js tests.

Chapter 5, Test Stubs and Mocks, dives deeper into Sinon.JS, with stubs and mocks that can replace application method behaviors. We examine how stubs and mocks can reduce application dependencies in tests and facilitate easier and more tractable Backbone.js application tests.

Chapter 6, Automated Web Testing, enhances the test infrastructure built in the previous chapters to run automatically, for example, from the command line or a continuous integration server.

This book is for JavaScript developers who are looking to create and implement test support for Backbone.js web applications. You should be comfortable with the JavaScript programming language and familiar with Backbone.js application development including the core components such as models, views, and routers, although you may be just learning the framework as you explore the testing topics of this book. Some exposure to testing methodology and technologies (in any language) would be helpful but not required.

In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.

Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "We simulate slow tests using the native JavaScript function setTimeout()."

A block of code is set as follows:

describe("Test failures", function () {
  it("should fail on assertion", function () {
    expect("hi").to.equal("goodbye");
  });
});

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

describe("Test failures", function () {
  it("should fail on assertion", function () {
    expect("hi").to.equal("goodbye");
  });
});

Any command line input or output is written as follows:

$ mocha-phantomjs chapters/05/test/test.html

New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: "clicking the Next button moves you to the next screen".

Feedback from our readers is always welcome. Let us know what you think about this book—what you liked or may have disliked. Reader feedback is important for us to develop titles that you really get the most out of.

To send us general feedback, simply send an e-mail to <[email protected]>, and mention the book title via the subject of your message.

If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide on www.packtpub.com/authors.

Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.

$ git clone https://github.com/ryan-roemer/backbone-testing.git