forgot to tick the resolve issue box whoops

so use normal brackets instead of square ones right? understood

issue resolved

A known number of values with entirely different meanings should be represented as a tuple, not an array or a list. Use appropriate datatypes!

Do not ask for rounded results. This is documented.

Thank you!

Lua translation!

Yup, the updates do not change any part of the functionality at all. The changes just update the assert equal syntax in the fixed tests. The part of the random tests with the customized assertion messages was not touched whatsoever since I was already using the "newer" syntax because the older syntax doesn't allow you to customize messages

Would you please review this fork?

I think it looks reasonable, but I know nothing about C#, I don't feel confident to approve it myself, and this kata is peculiar and particular in its testing.

.

Makes sense, Thank you.

Please don't reinvent testing. Test function return values instead of capturing console output. This way, when tests fail, there is no debug output.

Read documentation and test suites of kata you've solved. Also, ask Discord#kata-ideas whether or not this is a duplicate.

Random tests have been lowered to 55, that is already a very low number. Node 18 enabled too, so your solution now runs 2x faster at the very least compared to Node 8, so closing then ^^

Description is now language agnostic.

This is not a cheat, it's a valid optimisation.

You need tests with random word lists.