That's an exceptional approach, and a good reminder. No need to reinvent the wheel. :)

Yeah... I probably should have stripped the leading and trailing punctuation from words like you, but it was much more satisfying to just not remove '-'s. Kinda like saying, "Up yours, t-rex!"

No problem, before I try to solve a kata from scratch I look for what functions are already available.

Thank you for a wonderful feedback, i modified some of the description but not all of it , and also thank you for the test cases !

I've added those lines to the initial modifiable test cases for Python. I'll go ahead and do the same for the other languages too.

I don't know how to see your kumite. It doesn't appear under the kumite tab for me (for any language selected). The tests are really old (or in the case of Python and Haskell, translated as literally as possible from the old Ruby tests) and so could probably be improved but the tests are locked now so I can't change them.

Do you mean I should set up the constuctor instead of describe it?

I'm not sure how to avoid this. If you have some better insight into using the Python test suite, please let me know (or feel free to edit).

Ball and Ghost classes are preloaded.

Allright, didn't notice that mistake, resolved!

Added example test cases!

I agree. It was slightly weird to do the Ruby version and see a JS example in the description. Having an example test case would make it easier for others to see what is expected - or at least make language specific examples within the description.