.

thanks Johan

JavaScript by convention uses camelCase (except for constructor functions, which are capitalised). Please follow this convention.

It is possible to from now on ask for generate instead of Generate without invalidating existing solutions, if you consider that important. (I don't. As long as you're in Beta, it's fair game.)

Second example test fixed for you - had a spurious space after the last \n.

It really doesn't matter either way. It's not harder or easier, just (very slightly) different.

maybe not - hmmm. i'll have a think about removing it :

thanks for that - i'm looking at the testing API so haven't quite got my head around it all just yet :) your feedback is always helpful :)

That's like negligibly marginally easier, which also doesn't add to anything.

By this rate, you might as well add input validation to make it "harder" (but don't, because that's just annoying).

because it's easier to solve WITHOUT the linebreak

The description still needs to be fixed ;-)

Needs random tests

Why trailing line break?

thanks mate - have solved the second test issue - damned copy/paste errors! lol i THINK it now looks better in the description

This was a fun kata! The instructions were clear and I enjoyed solving it. Second test case is broken, I think it needs a space before the first hash. Also, there's a way to present your code in code blocks instead of markdown which would make the example in your description a lot clearer.

Oh, duh. Can you tell this is my first kata?