test case coverage is wholly insufficient.

test case should run a loop from 0 to 100 and compare submitted solutions to the correct one. most of the solutions submitted by users are all wrong

Again, counterintuitive behavior. Also, somewhere deep in other comments, we find the real spec. Prepare all pizzas first, then cook them all in batches of 5 simultaneously. this is not how pizza's are cooked IRL. Sure, you can hide any lack of specs behind a "puzzle" tag, but still... what looked like a great kata, turned out to be an annoying one instead.

What a rabbit hole. Can an oven be opened to take out a pizza and put in another one, or do all 5 pizza's need to be inserted at the same time?

ok, from sample tests, I see half minutes, so there is my answer ..

This is bothering me:

The two pizza chefs can work on the same pizza

Both prepping and cooking a pizza has a fixed time (3 and 10 minutes). Why even mention then that 2 chefs can work on the same pizza, unless there's a hidden spec that preparation would go twice as fast all of a sudden?

python new test frameworks

see this

• 10 random tests are not enough to prevent false positive solutions.
• Edge cases should be specifically tested.

In sample test at 'add_cash' ans is 'Jeff has 118', but in really 'Jeff has 88' *In python

This Kata was fun. But it had confusing wording regarding the "check" method in the instructions.
It me a while to figure out that check really meant tranffer money to from a user to another user.
Not, check the status. Another way of thinking of it is like "writing a check" to another user.
Maybe use give_money or transfer_money woudld be better names for this method.

I have these error when attempting...

"Joe's checking account is disabled.
Log
Raise a ValueError
Jeff doesn't have enough money.
Log
Raise a ValueError
Joe can't withdraw 50, he only has 40"

I tried different ways and I don't know how to enable Joe checking_account?

Very Nice Kata , I learnd a lot From It Ty .

Python: the random test assumes the class must have a public property named balance (or its getter), but it's not specified anywhere in the Kata description. The tests should not rely on the implementation.

Fix: https://www.codewars.com/kumite/64b57ce627f2c91a8a97f07f?sel=64b57ce627f2c91a8a97f07f

OP solved it, closing