python fork to address poor quality test cases (which affects ALL languages, but I'm fixing python at least)

for example, as I post this, the two latest solutions are both wrong: a, b - it's kind of silly how the tests are failing to catch very common problems, and it lets down solvers that are genuinely solving it themselves instead of trivializing it with built-in functionality

my fork generates reasonably exhaustive tests (instead of randint) for lengths 4 and 5 which will catch close to all unintentionally incorrect solutions.

Can someone explain to me why converting a string to char with charAt() in java adds 48 to the resulting int?

Haskell:

initial solution setup does not provide function signature type

Python function name should be in snake_case

Hi! In C++ it allowed me to complete it without logical errors only with one test case:
if(sperm == "XX") {
sperm = "Congrats....female";
}
sperm = "Congrats....male";
}
So if there is input different than "XX" it will pass too. I think it will me more interesting if the test cases brings error for input different than "XX" or "XY" and it will lead to use of "else if". Cheers!

Actual and expected are swapped in C#

This kata is a subject to deduplication process here: https://github.com/codewars/content-issues/issues/176.
Please join the discussion to help us identify duplicate kata and retire them.

I think the test case should also test if the original array has been altered or not. Saw someone saying that it's not a best practice to alter the array directly and the highest vote for best practice did altered the original array.

D translation

C# fork to add random tests (author of fork and author of kata inactive)

NASM translation