I’ve come across a pattern where I’m working on some system without formal acceptance testing, but it’s known to be good in its current state.
My favorite way to quickly get to a place where I don’t regress is to spider the existing system, then save its output in text form, in the repository (usually in a directory called
This is useful for web systems, capturing the HTML, but it’s also useful for any system that at some point passes through a flattened-to-text output.
I plan on either using or writing a more generalized system. Do you know of one, or should I go ahead and write it?
An example of a project that does this is here: https://github.com/exad/zu/blob/master/test/run
With almost no intervention the tests end up producing a pretty thorough coverage.
Of course, this does not replace more detailed acceptance testing, and certainly does not replace unit testing, but it can be a useful tool.