retired

Duplicate?

• No sample tests
• No random tests

https://docs.codewars.com/authoring/guidelines/submission-tests#random-tests

Fixed.

Short and sweet!

Why are there no tests that checks max < base?

There are tests where max < base, but with the wrong result, e.g.:

assert.equal(words(10, 4), 10);

The number of words needed to read numbers up to 4 is 5 (including 0) or 4 (excluding 0), not 10.

Same bug in random tests.

All Solar Systems will start with the Sun,

test.assert_equals(jumbled_solar_system([]), [])

This Solar System doesn't start with the Sun.

Both things solved

IMHO the best solution is:

• no precision requirement in description
• default tolerance in new languages (including python)
• 0.01 in javascript for backward compatibility

The "round to two decimal places" was there originally since the beginning, and the original Python translation translated the requirement, so the large tolerance is not something introduced by this fork.

If you think that 0.01 is too much, we can adjust it to a reasonable value in all currently available languages (1 approved and 1 pending). OTOH I wonder if 0.01 is not good enough when talking about ohms and resistances?

A tolerance of 0.01 is unreasonably large. In languages without backward compatibility problems (all except js), the default tolerance is ok.

.

wait, strings can be compared??!

you are calling the function, not returning a new function as asked by the kata