Thank you for your advice.

You can try. But keep in mind that everything you put in there must be properly tested, and that the general task might still be viewed as "not really interesting" (depending on what methods you add, ofc). So if I were you, I'd first ask myself if I'm up for this.

Did you already read the documentation about authoring? The main problem is the "Idea" part, so far. I mean, I get you want to create the kata. But first, ask yourself if you create it for you or for codewars. If that's for you, that's perfectly fine, but the kata might not survive the beta phase. If you try to create it for codewars, the actual question becomes "does codewars need this kind of kata?" and here, the answer might be "no" (again, depending on what you put in the kata/class. But there are alredy a lot of kata about basic class creation).

I hope I'm not discouraging you...? x) That's not my goal.

Cheers

So what if I change things to include some new methods

I fear that won't really change the matter, because creating a basic class has already been done too.

It is about creating a class

Calculating median/mean/mode has already been done many times. If you republish this kata, it will immediately be marked as a duplicate.

You can ask for a list, but then you need a list for a single element too: [18] instead of 18

I suggest about 100 for each method

Ok
But how many random tests should I have.

I suggest you to unpublish the kata until you have random tests, otherwise some warriors will instantly destroy this kata

And by random tests what exactly do you mean. I am new to authoring kata.

Ok so instead of outputting list for mode can I ask to return the larger number

• Function names should be median, mean and mode.
• Returning different types for the same function is bad practice.
• There should be random tests

Actually that was my first kata. Sorry I have no experience. Will try to do my best in the next one.
So sorry!

Actually that was my first kata. Sorry I have no experience. Will try to do my best in the next one.
So sorry!