I was just reading about how parseInt works, and how you should always pass the second, radix argument. For example: parseInt(“012″) returns 10, whereas parseInt(“012″, 10) returns 12.

We use Jshoulda for our javascript tests. http://jshoulda.scriptia.net/ We were getting weird behavior with Screw.Unit that I think was self-inflicted so we tried something different.

Screw.Unit is nice and pretty simple to use, especially if you have used RSpec.

You might also want to check out JSpec: http://wiki.github.com/visionmedia/jspec

Re: mistake in my tdd style, I’m definitely not a TDD purist.

I often follow a pattern of refactoring as I take it from red-to-green, while re-running the tests to make the sure the green ones are still green (you’ll see it in a couple places in this kata). I guess it’s not really red-green-refactor though in that case.

Also, in “real life” development I might write a bunch of larger-grained tests right off the bat rather than one at a time, then write smaller tests on a one-by-one basis until all of the high-level tests pass. I think it’s pretty efficient (for me at least).

Cheers,
Dave

I noted a possible mistake in your tdd style. For example, at 8.30 you refactor “add” method introducing “calculateSum” method when you are in red bar