Yeah, this is the mailing-list of Magritte and Pier, even-tough it still called smallwiki ... maybe we could create an alias and migrate slowly, but I dare that this is not that easy as the name change was? Ahh well, this is more a kernel test, not a persistency test ;-) I didn't had time to write tests for the persistency or the commands yet. There are some empty skeletons for the commands already. No, the method #snapshot is not called from within Pier, I guess that it should be manually executed from a workspace (maybe also from a regular thread), if the user wants to create a snapshot. The key thing is the logging of the commands that happens in #log: and is called automatically after executing every command. There are different subclasses of PRPersistency: - PRImagePersistency: this mock-class is finished, it is basically intended to test and try out the whole persistency mechanism. It keeps the commands and snapshots in ordered collections within the image. - PRNullPersistency: doesn't do any persistency, it is basically intended to test other parts of Pier without the overhead of storing anything. - PRFilePersistency: this should do the same as PRImagePersistency, but it is not finished right now. Lukas -- Lukas Renggli http://www.lukas-renggli.ch