Tests should use approximate equality instead of rounding + strict equality. Affected languages:

• JavaScript
• Ruby
• Python
• Crystal

In JavaScript, I intentionally used a truncated form of Pi in order to point out that an incorrect solution could pass the kata.

(not sure if this amounts to a legit issue but thought I would post it anyway, see what the community thinks)

Adding fixed tests / altering the RTG would solve this.

Groovy Translation

python: assert_approx_equals should be used.

On java full suit of tests asserts this input "0X1e5" but on kata instructions is only defined for prefix "0x" and not "0X". I hope it helps. Maybe that information should be included on specifications.

Where i can leave my code to ask about his workable ?

Error messages in C++ present values with insufficient precision: see the question below.

Hi Taw,

Thanks for the Kata. By reading the challange too complex it tought me a lot.

Just as an idea:
Build in a check that is the trainee creates a "x class" in the solution; to point them in the right way.

Enjoy

Scala translation

No random tests in

• CFML
• Clojure
• C#
• JS
• Ruby

No random tests in

• C#
• JS
• Python
• Ruby
• TS

assertTrue && assertFalse should be used for fixed test of PHP

This kata is a subject to deduplication process here: https://github.com/codewars/content-issues/issues/165.
Please join the discussion to help us identify duplicate kata and retire them.