Miklos Megyes miklosme

In my last blog on this topic, I claimed that the choice to use RequireJS handcuffed you to the less than awesome experience of using a browser based test runner. I was wrong! Surprised? Yeah, me neither.

I describe my ideal testing experience to be this: Anytime something changes, my personal robot army runs unit tests and tells me what I broke without me having to lift a god damned finger. I'm a programmer, I'm lazy, that's why I do this; so I can automate my life, my code, my income, and just retire to an island while my robots run shit. I'm not quite there yet, but this is here to share with you, how I finally figured out step 1337 of this plan - Automated Javascript Unit Testing.

Get Some Background

In this post, I'm not planning to go deep into how to write unit tests, mock, spy, or any of that. This is going to be about where and how the tests are run, not how to write them. If you're just getting started with testing your RequireJS modules, check out [amd-testing][1] and [RequireJS + Chai + Moc

	// Written by Paul Kaplan

	var BinaryStlWriter = (function() {
	var that = {};

	var writeVector = function(dataview, offset, vector, isLittleEndian) {
	offset = writeFloat(dataview, offset, vector.x, isLittleEndian);
	offset = writeFloat(dataview, offset, vector.y, isLittleEndian);
	return writeFloat(dataview, offset, vector.z, isLittleEndian);
	};

	#include "SDL.h"
	#include <OpenGLES/ES2/gl.h>
	#include <OpenGLES/ES2/glext.h>
	#include <iostream>
	#include <string>
	#include <memory>
	using namespace std;
	GLuint programObject;

	class Graphics

	/** @jsx React.DOM */

	var Graphic = React.createClass({

	componentDidMount: function() {
	var context = this.getDOMNode().getContext('2d');
	this.paint(context);
	},

	componentDidUpdate: function() {

	// === Arrays

	var [a, b] = [1, 2];
	console.log(a, b);
	//=> 1 2


	// Use from functions, only select from pattern
	var foo = () => [1, 2, 3];