Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Presentations Test Driven JavaScript Development That Feels Great

Test Driven JavaScript Development That Feels Great



Toby Ho shows how TDD for JavaScript can be fun, providing tips and tricks on how to keep the TDD experience fast, flowing, and enjoyable.


Toby Ho is a JavaScript developer in Atlanta. He blogs at and is passionate about helping others learn. He is active in the open source community where his proudest work is Test’em - a JavaScript test runner.

About the conference

DEVNEXUS is the Southeast’s most exciting conference for professional software developers working with languages, tools, frameworks & methodologies connected to the Java platform. With attendance of over 1200 people, 10 tracks provide a fantastic learning experience for Core Java, Web, Cloud, Mobile, Data & Integration, HTML5, JavaScript, Alternative Languages, Agile & Architecture, UX/Git/DevOps.

Recorded at:

Aug 02, 2014

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Should clarify benefits of TDD vs. benefits of unit tests

    by David Karr,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    This presentation makes a small mistake I've seen several times in other TDD presentations. It claims benefits of TDD that are actually the benefits of unit tests.

    Specifically, the presenter lists the following:
    * Reduced defect rates
    * Protection against regression
    * Better API design
    * Re-use tests as your specs

    These are all very good things, but except for "Better API design", these are all things that you get when you simply write good unit tests. One could argue that you could get better API design if you simply consider the concept of "design for testability" while writing your "code under test".

    To be clear, test-driven development is a particular strategy for writing unit tests and the "code under test". I'm not trying to say that TDD is not a good thing. I believe it is, although there are still some people who believe in unit tests, but not in TDD. The main reason I want people to be clear on the distinction between writing unit tests and using TDD is that I've often worked with teams who don't even accept the value of unit tests (versus the costs), but who have top-level managers who are pushing for their teams to use TDD.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p