Enforce no transactions on specs with delete tables strategy
What does this MR do and why?
We know using testprof
methods like let_it_be
and before_all
don't mix well with specs that are supposed to run outside
of a transaction (since they create one).
This change raises an error whenever a transaction is open
on these type of specs so the developer can fix it. |
How to set up and validate locally
Try running a migration spec that declares a variable using let_it_be
or defines a before_all
block. You should get a runtime error.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #425244 (closed)