Synchronized is redundant, commited my mistake.
It's about 30% slower than non-synchronized version.

general advise: you shoudl really read those things:

• https://github.com/codewars/codewars.com/wiki/Kata-Creator
• https://github.com/codewars/codewars.com/wiki/Tutorial%3A-Create-Your-First-Kata
• https://github.com/Codewars/codewars.com/wiki/Language-JavaScript

My point is: even if your kata has what's required, the test suite is "sub-par": no describe/it blocks, assertions at the main level. Those are pretty bad habits you'll need to leave if you wanna author others kata. ;)

cheers

Thanks, put Test.assertEquals() inside a condition, works fine.

again, not with chai/node 10, or if properly put inside a condition (designed for the purpose, ofc):

for(...){
  let expected = ...
  let actual = ...
  if(expected!==actual) Test.assert...
}
Test.expect(true)  // needed so that at least one assertion is executed. Or put a fixed tests if you want

If I put Test.assertEquals() put inside a condition I get Max Buffer Size Reached

not if you use it:

• either inside the condition
• or if you use node 10 and chai

Test.assertEquals() will output a billion messages affecting time of execution

Added random tests

it's exactly the same than mine.......

Also, why throw error when you can just Test.assertEquals()?

No random tests.

The thing is should this solution pass?

ok

Your solution is just a little bit slower than the fastest one, so it should pass.