... because they are, although I do not remember were I know this from :)

yes I saw that. ;p

but considdering the stack trace: at /home/codewarrior/index.js:35:36...?

edit: yep, confirmed, it's the assertion. I just checked against the sampel tests with an empth body. Weird... Means the files are concatenated in JS too...

Test.assertSimilar(getPINs(pin).sort(), expectations[pin].sort(), message )

Test suite calls sort directly on returned result, so it will crash on undefined falling out of user solution.

@hobovsky: sure it comes from the assertions? looks like it comes from the code of the user, no (but assertions could be at stake, yes)

This happens when your solution returns no value. You probably have some path in your code which exits the function witohut returning anything.

I agree that assertion could be improved though.

hi,

not an issue, a question. That comes from your code: at /home/codewarrior/index.js:35:36, so that's just an error in your logic.

If not already done before, reading stuff in there might help you to debug your code.

cheers

PS:

• issue = dysfunctioning kata, wrong tests or description, ...
• question = user having troubles to solve

;)