Thanks for the response and for the kata. I think this may because I'm new to Codewars and am still learning the flow. I hadn't seen a kata without premade sample tests before and had it in my head that passing the sample test was a prerequisite for attempting the kata, which looks to be wrong.

My impression of the test case comments was that it was default text provided by Codewars as instructions for the author to make sample tests--it didn't jump out to me as instructions from the author. I guess it may have been more clear to me if the instructions said "There may not be sample tests provided in your language for this kata, but the following are examples of expected output values: ..."

Older kata (many of the ones I created) don't have sample tests for all languages. There was a point where there just wasn't sample tests at all (as a feature) - it was always a blank area for you to write your own tests.

From a UX point of view, can you help me understand what was confusing? At what point did you read the comments and inteprete "This is just an example of how you can write your own TDD tests" to literally mean "these are just examples, write your own"? The comments in the test cases say that you should replace the examples, were those not helpful? Any suggestions on how it could have been more obvious?

Edit: To be clear, sample tests have nothing to do with passing the kata. You must attempt the kata to pass it.

After failing for a while to figure out why this wouldn't pass my code on the sample tests, I gave up and looked at the other solutions. I tried a handful of the successful solutions to see if I was missing something, and the server always responded with the same error it threw on my code: "This is just an example of how you can write your own TDD tests - Expected: 'expected', instead got: 'actual'".

I think this is missing test cases for the JavaScript version.