Kata

Approved.

reopening: if you checked that the O(log n) verison cannot pass the current version, you can close this one. but considering this solution is passing, I'm tempted to say that the perf tests aren't hard enough

Reduced the amount of assertions to 1000

very bad idea: doing so you're changing drastically the perf requirements. The idea was to silence the tests, and do more of them (because without all the assertions to print to the console, the code will execute faster).

You're supposed to use something like this:

    for _ in range(numberOfTests):
        data = randomValue()
        expected = ref_sol(data)
        actual = user_solution(data)
        if actual!=expected:
            test.assert_equals(actual,expected)
            break
    else:
        test.pass_()

the last line is about your last question. If you silence the tests that way and all results are correct, you need it so that at least one (succesful) assertion is done in the test.it block.

Note: if you're not sure about what you're doing, don't resolve the issue and wait for feedback. That avoids the need for raising another one.

edit: btw, you should have in your test suite a version in O(log n) of the solution, so that it's possible test it quickly, to tune the number of tests and the input range, making sure it cannot pass the tests. Maybe you already have that, I don't know: I cannot see the test suite, for now.

the random tests must be silenced if succesful: 10000 assertions are just killing the browser (note: don't forget to add one passing assertion at the end of the loop^, when all answers are good, and break the loop at first wrong answer). Once done, the perf requirements must be verified again, because the amount of data to currently transfer (assertions) is very time consumming, so maybe the setup won't be appropriate anymore

and fixed tests with small values should be present too in the full test suite

Great fun Kata !
Wrong function name in Solution Setup : square_spiral shoud be squared_spiral.

Reference solution should use an O(1) algorithm.

• No fixed tests in main ("attempt") test suite
• Tests should use nested describe/it blocks

https://docs.codewars.com/authoring/guidelines/submission-tests/
https://docs.codewars.com/languages/python/codewars-test