Let’s Code: Test-Driven JavaScript

James Shore presents a fascinating screencast
on rigorous, professional JavaScript development

Watch Now

Recent Advanced Episodes

Updates Monday and Wednesday

  1. Isolation Layer

    Mon, 26 Sep ’16

    It’s very easy for something like networking to extend its tendrils through your system, making future changes difficult. Providing a clear isolation boundary makes it easier to refactor. But our code, while nicely isolated, still doesn’t feel like it’s pulling its weight. We finish off our network event classes, then stop to consider what we’ve done.

  2. Over-Engineering?

    Wed, 21 Sep ’16

    By creating toSerializableObject() and fromSerializableObject(), we’ve very carefully isolated our network event from the actual Socket.IO transport layer. But is this solution over-engineered? Although our event structure is better isolated and more centralized than before, the new methods feel like boilerplate. Are we on the right path?

  3. Psuedo-Deserialization

    Mon, 19 Sep ’16

    We finish migrating our code to use our new NetworkPointerEvent object, including adding code to 'deserialize' the bare data object we get from Socket.IO and turn it into a proper NetworkPointerEvent instance.

Introductory Episodes

Full Series Now Available!

  1. Hat and Gown

    Fri, 12 Feb ’16

    Our series is complete! Where do you go from here? With the conclusion of this series, if you’ve done the exercises, you’re ready to act as a junior developer on a professional team. Now we talk about what it takes to graduate to the next stage of your career and provide some specific guidance about what to do to get there.

  2. Test Doubles

    Fri, 5 Feb ’16

    One of the most common testing techniques you’ll see in the wild is the use of test doubles, also known as “mocking.” We take a close look at this advanced technique. It’s seductive and easily abused. We rebuild one of our tests using mocks so you can understand the concept... and see what to avoid.

  3. Cohesion

    Fri, 29 Jan ’16

    Our application is done. It works. I’m not entirely happy with the design of our latest code, though. It lacks cohesion. In this episode, we wrap up our tab application with a look at three fundamental design forces: the DRY Principle, Decoupling, and Cohesion. We use what we learn to improve the cohesion of our application’s startup code.

An in-depth screencast about
Test-Driven JavaScript

You've taught me a lot this past year and have
been better than a teacher, a true mentor.
Jason Weden
I’m completely new to TDD and this is by far
the most comprehensive TDD for JS... your videos are
a breath of fresh air!
Adam Brodzinski
This is a gold mine... This will help a lot in my day job.
Timothy Myers
Love what you're doing. It's helped out our
team tremendously here at Sevenly.
Scott Corgan
I’m delighted with LCJ. It’s interesting and informative, and the
candid way you think aloud makes it personal and engaging.
You’ve done a terrific job.
Crispin Bennett

JavaScript Needs Test-Driven Development

If you’ve programmed in JavaScript, you know that it’s an… interesting… language. Don’t get me wrong: I love JavaScript. I love its first-class functions, the intensive VM competition among browser makers, and how it makes the web come alive. It definitely has its good parts.

It also has some not-so-good parts. Whether it’s browser DOMs, automatic semicolon insertion, or an object model with a split personality, everyone’s had some part of JavaScript bite them in the butt at some point. That’s why using test-driven development is so important.

What is Test-Driven Development?

Test-driven development (TDD) is a technique for ensuring that your code does what you think it does. It’s particularly relevant for JavaScript, with its cross-browser incompatibilities and hidden gotchas. With TDD, you express your intentions twice: once as a test, and once as production code. If the two approaches don’t match, your tests fail, and you’ve caught a bug.

TDD is a great way of catching the majority of programming errors. It’s not perfect, of course—in particular, it can’t tell you when your assumptions are wrong—but it’s very good at catching the kinds of bugs JavaScript is prone to.

Who am I?

I’m James Shore. I’ve been building applications using test-driven development and other Agile techniques for over 15 years. I’m a recipient of the Agile Alliance’s Gordon Pask Award for Contributions to Agile Practice and I wrote a book called The Art of Agile Development.

What You Get

This screencast series focuses on rigorous, professional web development. That means test-driven development, of course, and also techniques such as build automation, continuous integration, refactoring, and evolutionary design. We test against multiple browsers and platforms, including iOS, and we use Node.js on the server.

All videos are DRM-free, available for streaming or download, and all source code is included.

The Videos

The series consists of four main channels. The “Recorded Live” channel focuses on real-world development, warts and all. It’s meant for experienced programmers.

If you’re a new developer, the “How To” channel is for you. It’s meant for beginners who have recently learned to program and are ready to start their professional career.

The “Lessons Learned” channel provides concise reviews of key topics, such as continuous integration, test-driven development, and build automation. It’s great for review and reference.

Advanced programmers will enjoy “The Lab”, our channel focused on exploring new tools and ideas.

Release Schedule

New videos are published every week. A new “Recorded Live” episode is released every Monday and Wednesday. Specials (“Lessons Learned,” “The Lab,” and “How To” episodes) are released when they’re ready.

“Recorded Live” and “How To” episodes are about 15 minutes long. “Lessons Learned” videos are typically about 15-30 minutes long, and episodes of “The Lab” tend to be about an hour.

I have learned so much more than I expected.
I really enjoy your approach to screencasting and
wish the series wouldn’t end some day.