AnsweredAssumed Answered

How can we run tests on production data without copying large amounts of data all the time?

Question asked by dscheffer on Dec 20, 2018
Latest reply on Dec 21, 2018 by jpotts

Hello Everyone,

 

We are thinking about integrating the Alfresco Content Services in one of our applications and are now confronted with the question of how we should go about development – in particular integration testing. We expect the ACS to harbour large amounts of data at some point in the future. This will make copying data to staging/test systems impractical. What would be ideal is if we could fire up a throw-away instance for development/testing that copies data on write from a production or at least staging system as we would not want our tests to corrupt the data all the time.

 

Has anyone had this issue before? How would you go about this problem?

 

We were thinking that we could implement a custom content store but this would only partially solve our problem because metadata would still come from the working store which is based on the RDBMS. This would result in discrepancies between the file contents and the metadata. We could also provide a custom implementation of the NodeService but it is not a supported extension point and we want to stay compatible with future ACS versions. Has anyone experience with custom implementations of the NodeService?

 

Thank you for any suggestions!

Outcomes