xD

Hi. Your code timing out has nothing to do with this warning. It just means the tests should be updated to a newer version, but they still work fine.

Make sure you select the right Node's version in the selector. Also, backup your code, click reset and paste it again.

Enabled v14, try again.

Because it requires Node v12 at least to work.

People often misuse "Best Practise" button. I would rather mark my solution as "Clever" if so.

Tests call random funciton first, and then check if your guess is equal to what it returned.

That's because in the tests, Test.expect is used instead of Test.assertEquals, so you don't see in the error messages the actual value. It's not a big problem here when the expected values are all booleans but it's a little obscure to debug, yes.

That's how javascript type coercion works. Not a kata issue.

There are 110 tests in javascript, your code isn't passing the last one. Not a kata issue, it's a problem with your code not being fast enough for that extreme test (each string has one million letters). Read posts below about it.