it would be better to show actual, expected and diff tables for the better user experience. You could look at the other kata that povide such an info. e.g. this one

in JS message like

Testing for:
pros = ["pros-1","pros-2","pros-3","pros-4","pros-5","pros-7","pros-8","pros-10"]
preferences = [["Code progammer","Computer repair","Cook","Data recovery service","Haircut","Handyman","House cleaning","Pet care","President"],["Code progammer","Cook","Haircut","Handyman","House cleaning","President"],["Computer lessons","Computer repair","Cook","Data recovery service","Handyman","President"],["Computer repair","Data recovery service","Haircut","Handyman","Pet care","President"],["Code progammer","Computer repair","Cook","Data recovery service","Handyman","House cleaning","Pet care","President"],["Code progammer","Cook","Data recovery service","Haircut","Handyman","Pet care","President"],["Computer lessons","Pet care"],["Computer repair"]]: expected [ …(10) ] to deeply equal [ …(10) ]

isn't very useful. I see the input but almost no information about expected answer.
That's in Random tests

thanks!

seems to work better now (anyway I fixed my solution before ;) )

in JS tests output is truncated like

Test failed for aroundFib(957): expected 'Last chunk 44842179940550505985582222…' to equal 'Last chunk 5402420264154456349058562;…'

so it is hard to debug

some names seem to be completely random, but there is some 'logic':

segments -> ss -> ß

result -> r

last -> l

I guess not all of them could be described by the word "easy" =)

thanks ;)

yes, it is already possible, but it's a huge amount so I guess I'll try to go through some purples as well (at least that few that I've already done in Ruby and haven't done in JS)

there are no more easy 3-4kyu JS kata left and not much easy 1-2kyu, so it wouldn't be fast I think

in Ruby

1. sample tests are broken, they have even syntax errors
2. style issue: function name coveredDots should be covered_dots
3. attempt tests expect strange non-integer results. e.g. 987.5909072547386 × 943.3982221769694 ↺ 73° 1240171 ̷≈ 931691.5061422606

in JS sometimes generateCoords generate illegal moves (a self-capturing move, for example) and a test (for instance, "Rollback more than amount of moves raises an error") could fail with a correct solution.
I was lucky to observe it at least once
maybe that could be fixed (or, at least, it could be mentioned in description that test could have some unstable behaviour)