Can you explain to me more clearly what is happening?

In example tests, there is a test case which looks like this: Assert.That(Kata.Hello(), Is.EqualTo("Hello, World!"));. Notice how Hello() is called without any argument passed in. You have to write your solution in a way which allows it. It should work for both forms: Kata.Hello(someName), and Kata.Hello().

You'd have to add something to the description along the lines of "In this kata, you are expected to write a function which can take either zero or one parameters." Even then, people tend to be bad about reading the description. I think the main problem is that this kata is introducing a concept that seems to be new to newer programmers, but it's not explicitly calling out what that concept is. A lot of people solving the kata aren't even aware that what it's asking for is even possible, so it doesn't register to them as "this is something I can control". Another idea might be to have the tests catch the exception and print out a more user friendly error message that says something like "Your function doesn't work when called with no arguments." A lot of people reporting this as an issue seem to have a problem comprehending error messages. At the same time, that's a skill they should be working on, it's not really reasonable to expect kata authors to have to do that just because a lot of solvers lack a basic programming skill.

This is not exactly what I wanted to ask. I would be interested to know what to change in the kata (in the description or in examples or something) so users will see their errors as their mistake, and not as a bug with the kata.

For example what made you think that the kata is buggy? What would help you see your mistake?

For hobovsky's question on how to help with the responses, I suggest instead of saying you are wrong, saying "the Kata is not wrong, if you are having issues tag the post with question".

when kata starts adjusting to my decision.

hence why people like me are asking for help.

The issue I see is that people are not, in fact, asking for help. They are dismissing the setup as incorrect right away. Only few users ask "why is my code wrong?" . Instead, majority of complaints is "this kata is wrong". Why?

Okay so I would say that:

• "I can't find a way to get around the problematic one" is not a sign of the kata being wrong. The example is there for a reason, and finding a way to solve it is a part of the solution. Intended way is to figure out how to make this test to work, and not to conclude that it is incorrect.
• I mentioned it somewhere below, and I would repeat here again: the challenge here is to make both forms work: hello() and hello(someName). IF a user solution can handle one way but not the other, tests fail.

What I would be really interested with, and maybe you could help me, is how to make it clear that failing test is a problem with user solution, and not with tests. It's already mentioned in the description. It is in example tests. What is missing? What sohuld I change to make users aware that it is their task to make things work?

1. yes
2. yes, but I can't find a way to get around the problematic one, hence why people like me are asking for help.
3. YES, but instead of finding answers, I find replies like this that don't help, and just tell us we are wrong but not what we are wrong about to help solve the problem.

Sorry if this comes out rude, but I am getting tired of asking for help or looking at other's cries for help and seeing nothing but "Your code is wrong, read the description again", and marking the issue as solved without addressing what they got wrong to begin with, or what they might have gotten wrong.
This is more of a complaint in general and not with you in particular.
Please take no offense.

EDIT: I realize that was an extremely rude rant. I also realize people like me think the issues area is where to go when WE have an issue with OUR code. It is supposed to be for issues with the Kata itself.
Sorry (Geez, this is embarassing for me)

Did you read the description?
Did you look at example tests to see what is expected?
Did you read questions below in this discourse, and answers to them?