updated last test to only do 50
can you verify if that helps fix the issue?

also there was a note in the description saying the last test was flaky

moved the last test to do only 50 times can you verify?

Thanks for pointing this out.

I can add a test to clarify that the string type should be converted, based on getter access? Or rather, what do you think would make more sense, and make the kata more useful?

cool and awesome.

That'd be great. I put in an honest attempt at figuring out why the last test was sketchy.

I'd be interested in finding out what it is.

cheers.

yeah i spent the better part of a day trying to figure out what the problem was as well. i am pretty confused about it.

Interesting. Let me know if you find what the issue is. I'll keep looking when i get more time. It is happening in the last test case, this much i know. haha.

I'll have a look at it this weekend.

Interesting I didn't know that arrays could do that in javascript. I am going to add a test case for it and update the description.

Ah, I hadn't thought of that. Good point.

I updated the tests to also check for arrays.

Thanks for the feedback, Glad you enjoyed it :)

Did I do this correctly?

Thanks for catching that. It looks like in does iterate through so 'a' in ['a'] is true or 'a' in ['aa'] is false. would be how to use it?

Also, I changed the example back to == instead of in.

I created some static tests. And moved the code to the hidden tests.

Is there any documentation on the translation process?

Didn't know it was available. Still need to get into the docs.

they both check for equality. Stylistically I am led to believe that the keyword "in" is usually preferred.

See: http://stackoverflow.com/questions/12774279/python-how-to-check-if-a-variable-is-equal-to-one-string-or-another-string

But in that example it is checking multiple strings inside a tuple.