This is the only way to do it my fellow coder ( ͡° ͜ʖ ͡°)

Thanks!

best solution for sure!

Implemented as suggested.

Thanks for giving me a hand with this, might come handy in the future.

Write a reference function and use it inside the assertions (like Test.assert_equals(get_char(random_value), solution(random_value))).

Or for this particular case it'd be easier to simply save the expected value in a variable (e.g. expected) beforehand and then do Test.assert_equals(get_char(random_value), expected).

Now I got what you meant by useless comments. It was that TODO stuff, no the Test.describe. These are gone now.

Any tips on how should I concele the refrence solution in Test.assert_equals?

The comments are still there.

You should never inline the reference solution in Test.assert_equals arguments. The user can remove his function definition and will get an error message with a ready solution.

Removed the comments and added random tests.

No random tests.

Useless comments in sample and final tests.

The function name should be get_char.

Can't be approved, description has to be updated.

Hi , I can't seem to find a solution to this problem , but will keep on working on it . Thanks

Hi , I will look into this thanks for letting me know about this issue appreciate it

The 14th python (random) test case does not work:
Testing for 01:06
'30:36' should equal '0.0:0.0'

Edit: just noticed this is only the case in 2.7.6