I ran their code and discovered that it passes if the test is modified from assert.strictEqual to assert.equal, if that helps.

Please when reporting an issue, provide the code that gets that error. About what you said, change Node version to another one, and you'll see you're returning a function instead of a string in that test. I agree the error message in Node v18 is confusing, but I don't know why it shows that, so I'll leave the issue open just in case anyone else knows how to fix that.

language JS

how to understand this: expected "" to equal ""

I spent far too long trying to make this produce camelCase - the description of the problem is fine (I should have checked it more carefully) but the name of the challenge would probably be a lot clearer as PascalCase.

This was originally in Haskell, tho. Look at the language list, the one at the top is always the oldest. Tbh entire kata should be retired for garbageness.

Apparently this is resolved by latest JS fork.

work

The expression (as strings) (actual) == (s->expected) is false: 
actual=`EYkrllZpAJRwwwcMjgjKpTahMiegHWpp` 
expected=`EYkrllZpAJRwwwcMjgjKpTahMiegHWpp`.

Why it will be fail?

This question is wrong, this is PascalCase, not camelCase.

basic test - OK
attempting - errors

does it kata work for Go language?

thanks

All words uppercased is PascalCase, not camelCase.

That's a problem with your code, not a kata issue. Print the input, see what it is and why your code fails.

I like how we needed to return an empty string if given an empty string... As it was not mentioned in the description, unless this is a known step in all challenges that I did not know before today. Maybe it's because I used an imperative approach? Sorry I'm still learning.