Kata

Sample test should instantiate the class or the initial function should be made static.

for me, it gives an error: expected "Hey your own test case" but it was "Hey your own test case!" -- and I haven't added any "!" in my code

Nice job for your first kata. I would suggest more test cases to optimize the testing. I also would take a quick look at the kata details/instructions. They are worded with a bit of ambiguity in terms of where the exclamation should go. I had to look at the assertion in the sample test case to make sure what to submit.

make them use an if statement to greet females different then males

Cannot get any simpler. Would be interesting to have to add not only "Hey" but a few other variations, like "Hi" or "Hello", randomly selected from a list, to make it a bit more interesting.

Write your Katas just like you'd want to see them!

"My First Kata" in the title isn't really necessary, and neither is the apology at the start, as someone already pointed out.

Also, even though it's unlikely that someone would hardcode a simple Kata like this one, you should still add some random tests to prevent that. If you're just starting out, I'd be happy to help you out. :)

Do not apologize is is your first kata! Also I do not know the name Toom, could we use Tom instead?

too easy for 8kyu tbh

The solution shall assert if the input is a string or not

Should go for the "learning to program" level.

Greetings Why do you request a name type Object in the function? Should it not be type string?

As noted by others, there is plenty of simple katas like this, I would suggest deleting this one.

C# Translation translation added! :)

Props for creating!

Haskell translation added!

Sorry guys I was just trying out creating a kata lol

Furthermore, there are currently already a huge excess of such beginner level greeting-type Kata that literally take next to no effort to author so I would recommend unpublishing this Kata and coming up with a much better and original idea.

JavaScript version needs more test coverage; only 6 fixed assertions in the entire test suite is far from enough in terms of preventing logically flawed and/or hardcoded solutions. The most common way to increase code coverage is by the addition of 100+ random tests so please add these.

Crystal translation with random test cases you can basically copy and paste into your own Ruby translation (why don't you approve it yet your own work :D?), cheers :)

Imho but I think need more test cases in the kata

I'm pretty sure there are other katas like this, althogh I'm too lazy to look them up ;-)

Also, you may want to add more tests and even random tests, although it might not be necessary for such a simple kata.

Cheers