Ok, thanks for explaining that. It does make sense - though I would suggest a grace period (7 days?) before a kata is retired. As someone who doesn't visit CodeWars all that often, and just woke up one day with an idea for a kata in my head, the experience of submitting a kata so far hasn't made me want to come back or recommend CodeWars to others.

Also @anter69, please pardon my sarcasm. What I like about this kata is that it takes a problem that everyone is deeply familiar with but flips it in order to introduce a language-fundamentals concept (infinite sequences) that a lot of junior developers won't be familiar with. So the fact that FizzBuzz is a cliche is almost the point.

Anyway, I'll resubmit it with the suggested improvements when I have time! Thanks all.

"and the point is also to sort out the katas that are up to a certain standard "

.. isn't this the function of beta testing? i.e you don't let a kata advance beyond beta until it's up to a certain standard. Retiring a kata after only 1 day in beta seems a bit Spartan.

Oh you don't say? There was me thinking that FizzBuzz would be new to CW... how stupid of me.

Uhh it got retired? Isn't the point of a beta-testing process that the kata is iterated upon? :-/

ah yeah you're totally right! I've updated it, as well as the tests + implementation.

"rating of the kata" - because it would make it harder? I'm not sure about the rating tbh, was just a guess.

not sure what you mean :-/

Is it running slowly for you?

in away I agree with you. I just wasn't sure what should happen for "invalid" input. Any ideas?

That's nasty. I didn't write that JS version but will have a look at it.

Fixed

Interesting idea. I would like to see an implementation of that.

cheers! btw I think it's something to do with the CodeWars testing environment. I had to move your MySuperTest class inside the describe block to get it in scope.

can you suggest how to improve it? This is my first kata so I didn't really know what I was doing.