While building a web site using MMBase we regularly come upon the problem of having both "real" content and "test" content in our site. The test content is needed to test al your pages while the real content is already being entered because it had to be ready before yesterday (of course!)
This test data really leaves a mess and I was thinking of some way to tag it so we can separate it from the real content - first thing that came to my mind was to create a /TestData/ object, and to connect all test objects to that object, that would provide an easy way to identify and remove the data again. But for this to work I would have to add explicit support for it on all places where there are nodes being added (Both in editors/editwizards and on user-submit pages) while I would really like a solution where I only need to put changes at one place.
Anyone (other?) ideas on separating test data from production data? (Or in general on how to go from development to deployment with some overlap in time)
thanks,
Simon Groenewolt Submarine BV
