It is not an issue, this is how Codewars works.

I eventually changed the code not to print but to return only and it worked. Thus the issue here is the testing algoritm expects a return value, not a terminal output.

perhaps there is an extra transition to the next line at the last iteration

Dificult Dificult dificult

Approved LosBlobbos' fork.

Removed TestFactory because it is too loud when tests are failing. Approved.

Rust translate

I did a while loop in for loop, but I kept getting time out...

https://docs.codewars.com/training/troubleshooting#expected-the-same

Probably because your code returns a wrong answer. If the only thing you did was replacing print with return, then your code only returns a part of the whole string.

When I use return Instead it is still saying I failed the tests

If all tests fail with some message similar to Expected 'Something' but got None or something along those lines (depending on language and assertions library used), it might mean that you are printing your answer to standard output instead of returning it from your function. This problem occurs especially often for people who do not understand the difference between printing a value and returning it, or when someone comes from some other competitive programming website which actually requires values to be printed and not returned.

You're printing the result to the console instead of returning it.

test.assert_equals(draw_stairs(3), stairs)
                        ^
#           Your function is returning None                    

Still dont know why

https://docs.codewars.com/training/troubleshooting#expected-the-same