I see what you mean. I will work on better descriptions when I have time later today.

The assertion message should not share the duplicate message with it block, I suggest you read thru the materials given before proceeding to resolve issues ^^

Also, you should add them to random tests too or else messages like None should return False is not informative nor debugging-friendly

Thank you. I have added assertion messages to all fixed tests. Let me know if they are not detailed enough.

Read 7th bullet point here You may refer to here on how to scrutinize tests and write proper assertion messages

I don't understand what standard is being addressed. Is there a link to best practices that I missed? Thank you.

With the current standards and being a 8kyu, assertion messages (inputs) must be provided to fixed and random tests at least to aid beginners in debugging

Thank you. Republished

With the issues addressed and closed, you can republish the kata.

Changed to margin of error.

Changed to margin of error on perceived time per JohanWiltink's comment

Rounding is not the correct way to handle floating point representation inaccuracy, testing with an error margin is. This is documented.

Round to 2 decimals.

This is not enough information. In addition to the required precision, the kata should also specify the rounding method (e.g., half-to-even), and when to apply the rounding (e.g., on the sum at the end).

Thanks! It works well now

No sample tests.

Phantom JS version