When scenarios rely on a large baseline dataset the team does not own, rebuilding it may be less efficient than tracking scenario changes and reversing them. Undo Changes restores the baseline by undoing those operations. section 18.6.1
A reset using Undo Changes follows this sequence:
- Track inserts, updates, and deletes during scenario execution, saving the information needed to reverse them in a change journal. section 18.6.1
- In a before-scenario reset hook, reverse the previous scenario’s journaled changes, then remove the processed entries. section 18.6.1
- Record exactly how data changed: knowing that a record changed is not enough to restore its original values. section 18.6.1
Reversing an update
If a scenario changes a field, the journal must preserve its original value so the reset can restore it. An inserted record can be removed during reset. section 18.6.1
