Hi,

Keep in mind that for easy kata, the best approach is rather along the line of do one thing and do it well. Which is the opposite of what you're asking for here:

For example:

• the use of the class. But why in the first place? There is no point to use a class with the current context because there is no state to keep and nothing doable with it (hence: a class without methods is generally a bad idea)
• the overall task: what's the interest of the result? Any application?
• the identifier of a class is supposed to be in PascalCase, in python

May I remind you that you're not supposed to use CW to build challenges for your students?

cheers

Nice emoji, but

• @test.it("Fixed Tests") && @test.it("Random Tests") should be used instead
• The user can modify the input

And the issues below as well ~~ (You should read --> test framework && authoring) (Or more info regarding the docs which is just on the left sidebar of CW ~~)

Duplicate of Sum of Array Averages

Python: function name should be in snake_case.

issue part:

• Still no fixed tests....
• no describe/it blocks
• not even talking about the task itself

I already gave you a link toward detailed documentation.Inspite of that, you keep posting new betas with every time the very same flaws. In case you didn't notice, this kind of kata has already close to no chances to survive the beta phase, but with the other flaws, it's definitely a "no go", sorry.

edit: those changes I ask for (coding aspects) are mandatory. If you keep ignoring those recommandations, you might end up seeing your hability to author kata withdrawn.

I need to a program to help me
What's the program?
I'm going to put random values for you into the parameter of the function

All of this is redundant. We already know that you will provide random values (if you didn't, that would be an issue).

Why are you asking for a str return value? If the return is a list of numbers, surely a list of ints would be a better choice.

The description has to be updated. It's pretty confusing in it's current state

Hi,

Well, might be you didn't get the info earlier... If you're interested at authoring kata, you (really) should take a look at the documentation before doing another try.

For instance, this one and the previous (already retired) have the following problems (mainly):

• lack of originality (this has already been done to death)
• the full test suite must have fixed tests and random tests
• there is absolutely no point to do 1500 tests or even more. You're just killing the browser of the user, doing so (especially in python, which displays every single assertion)
• there is even less than no point (...? x) ) to do 1500 tests when the whole possible range of inputs is... 125...

cheers

PS: an advise: you should unpublish this one (before it gets retired anyway)

• Description says nothing about negative numbers
• Returning multiple types is bad practice

• No random tests (despite having many tests still isn't considered as being random)

• 3000 tests is just too excessive, 100 is enough already

• Python new test framework should be used in test cases part

• Duplicate

Maybe you should read this in authoring better katas in future