Scott Gray wrote: > I haven't worked on it for a few weeks but I do have some code that > can track changes on the GenericDelegator and then reverse them when > requested. At the moment it makes the test independent at the > component level, mostly because the was the easiest place to do it. > I've tested it by exporting the data from a fresh install, running > the tests, exporting again and comparing the differences and at the > moment the only data that gets left behind is anything coming from > async service calls.
My code doesn't require anything fancy. It just makes a backup copy of the entire data folder, and restores it between test runs. It was easy to do this, then try to have some filter that rolls back a complex series of changes. > I'll try and make some time for getting it to work at the test level > over the next couple of days and then put a patch in jira for > review. Of course the problem with committing it is that a large > percentage of the tests will fail because they depend on the tests > that came before them. Then they shouldn't be a separate set of tests. Whatever granularity we decide upon, the individual unit *must* be completely self-contained, be completely automatable, and not have any external dependencies, be it manually run configuration(creating entities thru some front-end, etc), or requiring some other piece of automation be run beforehand.
