Book Image

JavaScript Unit Testing

By : Hazem Saleh
Book Image

JavaScript Unit Testing

By: Hazem Saleh

Overview of this book

<p>The largest challenge for many developers’ day to day life is ensuring the support of, and assuring the reach of, their product. With the ever increasing number of mainstream web browsers this is becoming a more difficult task for JavaScript coders. <br /><br />From the beginning, JavaScript Unit Testing will show you how to reduce the time you spend testing, and automate and ensure efficiency in guaranteeing your success.<br /><br />JavaScript Unit Testing will introduce and help you master the art of efficiently performing and automating JavaScript Unit tests for your web applications.<br /><br />Using the most popular JavaScript unit testing frameworks, you will develop, integrate, and automate all the tests you need to ensure the widest reach and success of your web application.<br /><br />Covering the most popular JavaScript Unit testing frameworks of today, JavaScript Unit Testing is your bible to ensuring the functionality and success of all of your JavaScript and Ajax Web Applications.<br /><br />Starting with Jasmine, you will also learn about, and use, YUITest, QUnit, and JsTestDriver, integrate them into your projects, and use them together to generate reports.<br /><br />Learn to automate these tools, make them work for you, and include the power of these tools in your projects from day one.</p>
Table of Contents (12 chapters)

Jasmine matchers


In the first Jasmine example, we used the toEqual and toThrow Jasmine matchers. In this section, the other different built-in matchers provided by Jasmine will be illustrated and will explain how to write a custom Jasmine matcher to have more powerful and descriptive testing code.

The toBe matcher

The toBe matcher is passed if the actual value is of the same type and value as that of the expected value. It uses === to perform this comparison. The following code snippet shows an example of the toBe matcher:

describe("the toBe Matcher", function() {
    it("should compare both types and values", function() {
      var actual = "123";    
      var expected = "123";
      
      expect(actual).toBe(expected);
    });  
});

You might question the difference between the toBe and toEqual matchers. The answer to this question would be that the toEqual matcher provides a powerful mechanism for handling equality; it can handle array comparisons, for example, as shown in the following...