Not an issue ~~

Not an issue ~~ (it's always from left to right)

So many people doing it like this. Pretty crazy.

Any idea what the solution is to this issue? Is it a testing issue? I'm having the same problem.

Bi-directional as in moving the cups left-right && right-left as opposed to one way? Not entirely sure what this means since I'm prety sure my code is correct but running into the same issues as other posters on the 2nd test when submiting.

I'm having this problem as well. My test in irb doesn't come back with any problems in terms of the split or adding the numbers up. is the 9th(ot whichever that fails) test the first tie? Because the tie in the three test cases work, I'm wondering if it's an issue with the string?

Probably when you split the input, you will run into problems with numbers with 2 digits or above, as they will all be split into single digits and mess up your final answer.

Testing with 10 cups
start: 0 swaps: 0,9,9,3,3,7,7,8,8,2,4,5 swaps length: 6
Test Passed
Nope! Expected 1.

Console log of the params didn't change yet test expected two different results for same problem.

Testing is broke and does not support bi-directional movement

The test is broke. He made a comment last time saying he intentionally used the word 'swap' as it should 'imply' bi-directional movement but I guess somewhere along the lines he decided that bi-directional movement wasn't going to be supported.

@mtthw123 Glad implicit and explicit are two definitions. BTW there's a reason the words are two different definitions. Would have skipped this one if not for the discussion because implicit also means someone as has to assume. I guess you know what happens when people assume.

To further illustrate your own example "implies" there only to be one direction of movement.
For example, given the starting position 0 and the swap sequence [(0, 1), (1, 2), (1, 0)] Answer is 2

I don't know if you've been trying to fix the kata test but this is full of bugs. More than a few composite numbers you've erroneously you have evaluated as prime. Noticed it first at 81 and then over and over as I debugged your kata.

This is an error and unfortunatly cannot be resolved because 500+ solutions have been submitted..

The solution is to create a default value for the parameter according to the specifications of the kata :)