i added this fixed test to C.

(C translation)
I had a bad approach to accepting the sign which completely passed the full tests but correctly fails after I added this to sample tests:

do_test(".+25", false);

There is of course already one like it:

	do_test("2.+25", false);

but my original way of permitting the + handled that one "accidentally correctly" by noting that there was a digit before it without bothering about its position in the string. After fixing my solution I hacked it back into a fork, which shouldn't have passed.

Approved.

Approved

Just added them to Ruby and several other languages, now all of them have the mentioned edge cases

The test is perfectly valid since the kata does not specify any constraints on character range, a.k.a any character is to be expected and handled gracefully

Perhaps reading this might help ~~ Also not a kata suggestion

Not a kata suggestion

Not a kata suggestion

Above fork approved.

fork that adds repr(pin) to python so that the string literals are string literals instead of vaguely looking like string literals while actually being text plus quotes which is worse than showing nothing because it's misleading

well, the test output is poor, for example: testing for validate_pin('\') which is invalid syntax

In that case, your PC is unaware of the nature all edge cases provided by the kata on this site, and your code is incorrect because it does not handle these edge cases. Please look very carefully at the error messages to debug your code. Good luck.

Everything is going well on my PC, but the site gives an error on the combinations ( 123 ) and ( 09876 )