when you return you don't need to add the break couse you already breaking the code

[not a kata issue]

your code fails a fixed test, here is the error message:

'Should handle negative numbers. For input n = -13, m = -13: expected NaN to equal +0'

which means your code returned NaN for that test. then your code fails any similar test during the random tests

so, you need to rework your code to handle negative numbers

JavaScript: Passed all tests but, after clicking Attempt it shows another 2 tests that are not passed

python new test framework

Good practice for Python

For such a short string is not something to bother about, and it feels cleaner for this specific problem

exactly my thoughts!

Appears to be the case in Python at least.

Python new test framework

• "it works on my machine" is never a proper issue report.
• it seems like your code is incorrect when the universe dies out, i tried it with { 0, 1, 1 } and it reports the new dimensions as -4 x -6

Very impactful.

I'm having an issue with this test "do_test(0, 3, 3, gen_0, 3, 3, gen_0);", I get "Test Crashed Caught unexpected signal: 6"
But when I run the function with the same arguments on my own I don't get any error.

it's so easy for me. I'm very happy to improve my logic in javascript with codewars

I only return null if the input is 0.

This is not correct thing to do. What will happen if $a is 0, and $b is -1? What will your solution return, and what is the correct answer?

Your solution has a bug, it's not a kata issue.

In what language?