result may be passed right away, because the check is performed only on 'Hello World'

The same was happening to me. You should account that the same node list could be passed to function one more time, so anchors you leave must not confuse function

Nevermind. I've already figured out why it behaved so. Though I believe expected values would be good still

Nice kata though I'm getting strange results on it. I'm trying to solve it in JS. The first test case passes but the second fails with no additional info (I though you've already added expected values). The thing is that it seems that within the second test case it invokes loop_size func twice. Is it right?

No edge cases were explored though description didn't mention that. I suggest either adding note, that just ints are passed and for division no 0 could be passed as a second param or add tests for such params

The same from me

Test Failed: .1+.2+.3+.4+.5 expect to be:15
must be kidding

Test cases are very bad. I'm quitting of solving it

I think so

Such kata already exists
http://www.codewars.com/dojo/katas/5226eb40316b56c8d500030f

This solution made my day

I suggest change array in the description so that it is not sequence of numbers and especially indexes. As I started solving it with iterating through array looking for match.

this solution is very unefficient. I see no reason it to be voted up

Using RegExp seems unefficient for using when knowing position of the symbol

Test.assertEquals(parseInt('six hundred sixty-six thousand six hundred sixty six'), 666666);
why on Earth is sixty six written without dash?? is it by design?