@tobbe0xFF to add some additional background, the JS version was the original language this kata was written in. When I wrote the Python translation, it was not exactly faithful to the JS version because of the difference you noted. The other languages are based on the Python translation, which leads to the JS version standing out from the crowd. But the point of the kata is to solve a single concise task.

Also, there are some choice solutions that have made it into the pool of user submissions that others can benefit from seeing/sharing.

Thanks for your comment. Without it, I wouldn't have passed the kata.

I see your point, but the intent of this kata is to solve the challenge without imposing constraints on how to do it. It's basically a kata that introduces metaprogramming for some particular language.

Also, with the JS completions currently at a count of 227, removing that language is not really viable.

I think the javascript kata should be removed. I have looked at others solutions and they all work because the order of the tests are known. Language wise the feature needed (which exists in i.e. Ruby and Python) does not exist in Javascript so there is no true solution that would work in all cases and when test order is unknown.