There is 100% a bug in the C RandomTests suite.

The bug is that it expects the input string to be modified in place, and it ignores the return value of your "correct" function.

There is no equivalent bug in C++, nor is there an equivalent bug in the C BasicTests suite.

This requirement is not stated in the problem, and is unique to one specific test suite in one specific language. It's a bug.

The workaround to meet this secret requirement is that you need to overwrite the input string with the result, before you return the result. That way, the broken RandomTests suite passes.

I'm doing it in C and have the same exact issue. Not sure what's up.

I'm currently having the same problem.

Any insight as to what you did to fix it?

@ggolren :

Okay

Nope, its all good.

Congrats on solving it :)

Nope, Random tests are not broken.

I can confirm that. Since I did it myself just to confirm that. There is something wrong with your code.

I will give a hint if you want.

I highly doubt there is a bug in the random tests.

But nonetheless which language are you using, provide the test cases you are failing on (one or two will suffice if they are of same type) and provide your code marked in spoiler tags so someone can take a look

At this point, I am quite sure that there is a bug in the random tests that are done.

Everytime I try to submit my solution it fails on some random test. For the sake of completeness, I add that failing test case to the set of sample tests given. When I do that, the code miraculously passes the very same test.

I don't know how this could be a bug with anything other than the random tests. Is this possible to have fixed? -- I am doing it in C by the way.

Otherwise, it was a fun kata!