Unit Testing Javascript in VS 2012

development
20598

You’re a responsible developer – you write code, and then you write tests (or, perhaps you even write tests and then write code?). You also love good, solid frameworks that separate concerns and utilize dependency injection and inversion of control and all of that good stuff – you’re using MVC for your web applications.

But you have a little problem – your pages use Javascript, and that’s difficult to unit test, right? Not any more.

The Sample Solution

For this post I’ll use a sample MVC app – of course, the principles apply to any client side app using Javascript, but this is an easy example to use.

Create a new MVC project in VS, and then add this script to the Scripts folder. This script contains some Javascript for populating a country / state dropdown combo. This is the script that we’re going to be testing.

Chutzpah and QUnit for MVC via NuGet

You’re going to need a Javascript testing framework, and then the ability to run your tests. There are a few frameworks out there, but one I enjoy using is QUnit. But that only gives you the infrastructure – you want to be able to run the tests easily too. Fortunately, VS 2012’s Test Explorer is extensible, so you can add your own “test adapters”. And there’s already one by Matthew Manela for Javascript testing with QUnit called Chutzpah (there is a test runner and a Test Explorer extension – we’ll just need the extension for now).

Let’s create a unit test project and use NuGet to install the QUnit package.

  1. Create a new C# Unit Test project. Delete the UnitTest1.cs file.
  2. Open the Package Manager Console (NuGet) and make sure the test project is set to the default project.
  3. Type “Install-Package QUnit-MVC” to install QUnit for MVC (this can be used to test any javascript, not just MVC).
  4. In the Extension Manager, search for Chutzpah and install the Test Adapter extension. Remember to restart VS once you’ve installed the extension.

image

Writing Tests

Let’s create a test stub for our unit test. Create a new Javascript file in the test project called “StateDropDownTests.js”. Put in the following code:

/// 
///


module("State Dropdown Tests:")

test("test States", function () {

});

Now open the Test Explorer and click “Run All”. You should see the test come up in the list of tests and it should fail (since nothing was tested).


image


The Real Test Code


Since the StateDropdown script we’re testing accesses objects from the DOM, you’re going to need to add some basic elements. Fortunately QUnit has hooks for adding elements into a test fixture. Add the following code to the module to create the DOM element we need for testing:

module("State Dropdown Tests:", {
setup: function () {
$("#qunit-fixture").append(
'' +
''
);
}
});

Now add the following code into your test:

test("test States", function () {
postCountry = '';
postState = '';

var stateSelect = document.getElementById('stateSelect');

// the dropdown includes all the states PLUS a 'Select State' option
initCountry('US');
equal(stateSelect.options.length, 62 + 1);

initCountry('UK');
equal(stateSelect.options.length, 43 + 1);

initCountry('CA');
equal(stateSelect.options.length, 15 + 1);

initCountry('ZA');
equal(stateSelect.options.length, 0 + 1);
});

Run the test – and you should see lots of green! Our test is working.


I was going to write a follow on post about getting the tests to run in TeamBuild, but Mathew Aniyan from the MS ALM team beat me to it – here’s a link to his post about Javascript Unit Tests on Team Foundation Service with Chutzpah


Happy Javascript testing!