#11b30/3q6:0z:vV

i thought the problem was what you describe
and i solved it accordingly

approved

fixed

thanks

Updated the tests, so the error message will no longer show. Now, when a user's solution has failed 3 random tests it will trigger an early termination. Thanks for the suggestion, @Etoneja.

For a rookie warrior, this may look like an critical error, and not an regular exception.

The feedback error message does look confusing, especially for those unfamiliar with the test framework. I'll see about updating the tests so the feedback is less confusing.

The reasons may vary, but an author may want to terminate the tests early if it's shown that the user's solution has returned an incorrect result. This approach is best suited for test suites that may run for a "long" time (for example, say if it runs 100 tests and completes at around 11 seconds).

By raising at the first instance, you can:

• save time
• eliminate waste of excessive CPU cycles
• make it easier for the user to debug

Yes, it is intentional. In the following line: test.assert_equals(max_hexagon_beam(n,seq),ref_func(n,seq),allow_raise=True) you can see allow_raise=True. This means that an exception is raised at the first instance of an incorrect result.

The specific details are in the test framework documents: https://github.com/codewars/python-test-framework/blob/master/codewars_test/test_framework.py#L27

not an issue of the kata itself. This has been happening from time to time for the last few weeks. Copy your code, reload the page and submit again.

oh wait... x)
It's a draft. You cannot complete it. You shouldn't even have get there, normally. ;)

you should have had no doubts that you would become a programmer. your solutions here are really clever

it's 1+2+1+9+9 == 22

I've scribbled up a Python solution and it's ran through the tests correctly. Looks good! Thank you for your contribution.

Good idea