Second argument is passed in as list in example tests but tuple in actual tests. They are different objects and behave differently.

The right integer of the last argument is superfluous, it's not used in the task.

Please update the kata with new python test framework.

For even more undifferent emptiness, read up on positive and negative zero.

But please don't make a kata out of it. :P

Hi,

I fear the description is way less than sufficient... :o

And you need random tests.

cheers

same troubles here, and in addition: you expect us to actually do useless swaps: data.swap(3,3). Bad idea.

do the copy on your side, before sending it to the user, so that the user can mutate his copy (which makes far more sense, considering the function we have to use mutate the list)

The design of this kata is terrible... Instead of making swap a closure for tracking its calls (for example), you created a class which has only 1 new method for modifying the only new attribute which remembers this method calls inside a function not belonging to this class whose sole purpose is working only with the said class?!

You're not allowed to sort decrementally (starting from end of the array)? Maybe you should have mentioned that in the description?

You should use Test.assert_equals for comparison.

Nice presentation/context! Tho, there are some troubles:

• description: An instruction string is also given specifying the indices of parameters that you should >>>not<<< modify. Are you sure? Looks to me that it's rather specifically the part we have to modify. Either way, that means this part needs a rewording.
• do NEVER use Test.expect unless you provide a meaning full message => assert_equals
• do NEVER put sensible code in the preloaded part (especially in python)
• seems to me the rifle tests has something wrong: "1:3" -> shouldn't that rather be "1:4"?

Nice one, either way.