U return a string instead of a number.

Thanks Mike, you're such a generous soul

forever and always. xoxo

Thanks for the support, Sus. Hope you are able to implement something similar in your own solution. Feel free to message me if you need any guidance.

thanks for the feedback Mike - just remember to stay humble ;)

Hi Sus, just a little concerned by your use of the sort method. While it is certainly very easy to implement, I can't in good concscience upvote your solution. May I suggest you use a linear sort next time?

Beautiful code - and good to see you're not using the lazy approach

Out of the park, Sus!!!

Smashed it!

A very readable solution. Great coding Mike!

Nice work Sus!

Thanks scf for the heads up; the Python translation should also be edited now :)

I just saw that "hoe" is still in the python test case, in case you might want to edit it there as well.

You're probably both interested in this. Note that working with GitHub pages is easier if you know git, but you can learn both at the same time.

1. parseInt is meant for strings, not for numbers. Sure, parseInt(12.5) will return 12, but that's since it transforms 12.5 to a string (internally). Use Math.floor to get the next integral number (towards negative infinity).
2. You return a string, whereas you're supposed to return a number. The tests use assertEquals, which uses ===. The triple equality operator not only checks whether two values are the same, but also whether their types coincide (try 12 === "12").
3. Your returned string has a trailing ,. Keep in mind that , in "Expected <xxx>," isn't part of the expected value. That won't be an issue if you fix #2 above, though.

By the way, if you don't get answers on questions, feel free to ask on gitter. Also, make sure to use GitHub flavored Markdown to make your code easier to read.