It says greater, not better. It's clear imo.

Is the "handicap greater than 7" line meaning they are better (lower handicap) or worse (bigger handicap)? The tests kinda make it clear, but I think that can be confusing

I just googled that and found a whole new world, thanks for the info.

I did not know that there was a community centered around solving problems with the least amount of characters...

I do like the idea, I was thinking about the graph when I came up with the kata, so I'd say it's fitting. It's also dealing with moving predetermined value, so I believe the tag is deserved. I'll add it. Thanks for the suggestion.

I forgot about those => good

I did what I believe you meant. Testing a few numbers on rules 2, 3 and 4.

it's more math than actual stats, imo (if a tag is needed)

suggested tag: statistics

oh, just test a bunch of numbers, then. Like 0,25,60,80,100.That's way more than enough for the sample tests.

Wouldn't that make the final tests equal to the test cases? My problem is that I can't find a way to make them different while making both of them useful.

... I believe it's pretty clear ...

yup... looks like my eyes skipped that part of the sentence, sorry... :/

About the first point, I'm not entirely sure, what you want me to do, but I made it so the tests only test the rules rather that the length.

why not testing both? (rules + length)

I updated Rule 1 in the examples. The most outrageous thing to me was the fact that one f was italic and the other normal.

I don't mean to sound condescending, but I believe it's pretty clear that the inputs will be between 0 and 100 on Task.

Write a function curve that take an integer from 0 to 100 (inclusive)

About the first point, I'm not entirely sure, what you want me to do, but I made it so the tests only test the rules rather that the length.

about point 1, you can duplicate the testing code in the preloaded section (but don't rely on it for the full test suite)

edit: that is.... if you don't want the user seeing some parts of it. But I doubt it will be a problem?

Hi,

• the example tests have to actually test the function's behavior, not the code length only
• I don't find it clear, by reading the description, if the function will get values ouside of [0;100] as input...? Might worth a tiny update.
• there is a discrepency between the rules and the example:

If you're given 0 or 100 return the given value.

but

Rule 1: 𝑓(0) = 0, f(100) = 0

cheers