• The description needs to be fixed (with actual english)
• The specs od the tests must be given in the description (number of tests, typical size of the boards, number of bombs per grid)
• the example tests should be rewritten with an input format that actually make sense. Things like "- - - -".split(' ') do not make sense. The board display function and the description should also be aligned.

Cheers

description only talks about one value (field) even though there is actually two (cr, the starting position of the rabbit)

also, python's test suite seems to still use camelCase, but the full suite uses snake_case correctly

In case of timing parity, return the values according to the order in the queue.

Needs clarification: order in the queue is not defined.

I really can't make sense of how to resolve timing ties.

Hi, you have changed function name without"backward compatibility" which means all previous solutions will be invalidated. Please approve this fork with backward compatibility and improved testframework.

How does the jump work if the jumppower is an odd number? does it go up by (n/2)+1 and go down by (n/2) or vice versa?

could use tag: algorithms