Because the python test framework require them :) (I don't know hopw it works).

The most noticeable effect is that without proper describe/it blocks, assertion messages are scattered across the output window instead of grouped in collapsible sections.

Added it to bigger tests. For sample tests I'm really not sure how to structure things. Why exactly are these blocks needed?

Missing test.it blocks in sample/fixed/bigger tests.

Looks good on my side now.

Interestingly, it looked fine to me. But anyway, I changed the way I was doing the spacing, so hopefully it's fixed - please check.

Uh... this doesn't look right.

.

Thanks for the suggestion! Took some time to get all those tags in, but it does look better.

You should use code blocks for the array in the example, so that the i and j marker can align with the element more consistently.

Comparison:

[30, 50, 5, 30, 51, 10, 20, 99, 18, 30, 100, 33]

  i           j

[30, 50, 5, 30, 51, 10, 20, 99, 18, 30, 100, 33]
      i                          j

Ok, it makes sense now.

Those messages are showing the actual sorted list (the desired output). When I run your code on, for example [8, -7], the returned list of snapshots is [[-7, 8], [8], []]. So it's responding to the fact that your last snapshot is the empty list, not [-7,8].

I updated the message. If you try your program again, see if the message makes more sense.

Must be bug - hold on ...

When I tests my solution:

Last snapshot is not the sorted list [-7, 8].
Last snapshot is not the sorted list [18, 20, 30].
Last snapshot is not the sorted list [5, 10, 18, 20, 30].
Last snapshot is not the sorted list [30, 33, 50, 51, 99, 100].
Last snapshot is not the sorted list [5, 10, 18, 20, 30, 30, 30, 33, 50, 51, 99, 100].

These are sorted though?

Approved. Let me know if you find any issue with the translation.

Hi dukies_2000,

Are you interested in having this problem translated into other languages?

Regards,

brodiemark