Added random tests.

The debug format wasn't my choice, it was taken from the website referenced in the description which is why I have used that format.

I must admit I do neglect the description and focus on the code, something I could improve on I guess...

I'm sorry my strength isn't description writing or explaining, I prefer to give examples within the test cases. As for the detail regaring the debug I do state that it must be an array representation of the tape which is why I have more tests in the example test case section so it's easier to understand?

I agree it is missing a tag saying performance or something.

The beast test is easily solvable by using the right data structure. Take a look at Unnamed's solution, it's simple and gets the job done, no fancy algorithm or optimization there.

You are absolutely correct. Thank you. I've made the correction.

Regarding the 1) Checked.

Regarding the 2) I'm sorry, I didn't update the Example Test Cases accordingly to changes I did to the Test Cases.

Please do take a look and let me know if I missed anything or if there's anything else you'd like to see changed.
Thanks for your comment!

Forked: try if it works, as usual :)

ruby translation : we need to merge first error has occured

Done: overall tests brought up to 50 - 10 fixe, 40 random -, added multiline string checks :)

If you are ok with it, I would take charge of fixing the tests myself, as I have some ideas for it.

Also: translated into Ruby and Python, if you wish to approve them :)

Thanks,Fixed....^_^