A cached step carries the model's notes on what it did and why. Those notes could quote a value the test got from an environment variable, such as a password or an account number, and the cache file is committed to git.
Donobu now replaces each such value with a marker like [env:ADMIN_PASSWORD] before the entry is written. Web, mobile and HTTP tests all do this.
donobu cache scan [dir]lists committed entries that still hold a current environment value, and exits non-zero when it finds one- A value that drives the step itself is left as is and noted in the log
- Re-recorded entries say whether what they do changed, and whether the new recording is verified yet
- A click on save, submit, delete, pay or a similar control that the step never asked for is noted in the cache comment