Hello, For some time I've worked on a little project called oak-resilience. It aims to be a resilience testing framework for the Oak. It uses virtualisation to run Java code in a controlled environment, that can be spoilt in different ways, by:
* resetting the machine, * filling the JVM memory, * filling the disk, * breaking or deteriorating the network. I described currently supported features in the README file [1]. Now, once I have a hammer I’m looking for a nail. Could you share your thoughts on areas/features in Oak which may benefit from being systematically tested for the resilience in the way described above? Best regards, Tomek [1] https://github.com/trekawek/jackrabbit-oak/tree/resilience/oak-resilience -- Tomek Rękawek | Adobe Research | www.adobe.com [email protected]
