The problem description states "You cannot assume the size of the array". This solution will attempt to write past the end of the allocated memory if the words and added spaces exceed 1000 characters.

The problem description states "You cannot assume the size of the array". This solution will attempt to write past the end of the allocated memory if the words and added spaces exceed 100 characters.

The problem description states "You cannot assume the size of the array". This solution will attempt to write past the end of the allocated memory if the words and added spaces exceed 512 characters.

The problem description states "You cannot assume the size of the array". This solution will attempt to write past the end of the allocated memory if the words and added spaces exceed 256 characters.

The problem description stated "You cannot assume the size of the array". This solution will crash if the words and added spaces exceed 1000 characters.

Your code differs from the solutions in a small, but significant way. You'll kick yourself when you see it.

Even better would be to test that each color occurs with roughly even frequency. Otherwise, solutions that can return any color, but that favor certain colors, will pass.

I'm pretty sure some of your test cases want me to say a newly created ticket is invalid even though it matches correctCode.

Nope. Looks good.

Fixed the bracket. Thanks.

I switched to Test.assertSimilar() as you suggested. Thanks.

Ouch. Thanks for the heads up. I thought it was ok to use since the kata editor didn't complain. Fixed now.

(0xFFFFFFFF >> 2).toString(2)
// -1 !?! (Node.js v0.10.28, phantomjs 1.9.7)

This is exactly what we would expect if bitwise operands are treated as signed 32 bit integers, since the >> operator will sign extend its operands.

To avoid sign extension, we need the >>> operator.

(0xFFFFFFFF >>> 2).toString(2);
// '111111111111111111111111111111'

(0xFFFFFFFF >>> 2).toString(2).length;
// 30

Good point. In the description, maybe

(NOTE: a number has 32 bits).

could be changed to something like

(NOTE: Although javascript numbers are always 64 bit floating point, javascript bitwise operators treat their operands as signed 32 bit integers).

Your description states

count, an optional integer value for how many bits to include in the slice. If this argument was omitted, all bits after from should be extracted.

but it seems that none of your test cases omit the count. Additionally, it seems you expect us to treat a count of "null" as if the count were omitted, but "null" and omitted are not the same.