ManagedTransactionRule

Reports a transaction() callback that ends the transaction it runs in.

transaction() begins its transaction before the callback and commits or rolls it back afterwards, so a commit() or rollBack() that ends that level leaves the callback's remaining work outside the transaction, and transaction() then throws because the level is gone. The callback's top-level statements are walked in order, counting the transactions it begins itself, and the walk goes silent at anything it cannot follow. A generator callback is reported on its own: its body only runs once the generator it returns is iterated, after transaction() commits.