Interesting, this is essentially a record/reply framework at the db driver level. Usually I think record/reply testing is an anti-pattern b/c it's typically us

Interesting, this is essentially a record/reply framework at the db driver level. Usually I think record/reply testing is an anti-pattern b/c it's typically used against external systems (i.e. REST/RPC API calls) where the current state of the external system is not captured in the recording itself. (I.e. someone clicked around in the vendor's UI to make it "look like this", then ran record. However 6 months later when you need to re-record your test, the state in vendor system no longer "looks like this" so it's a nightmare to know if the test is failing due to a real regression or just changed data.) That said, copyist records the test data being inserted/setup into the db as well...so...huh, it might actually be a good idea.