Hi Edgar, yes, I agree. What I have in mind is to discuss on how to bridge the "standard" testing and deployment/delivering activities with Magnolia workflow (work - flow). In other words, how can you have a test in your CI to proof your Magnolia command? Are we able to CI a "fake" repo? How can I test if every component I did can be instantiated and run as expected? Can we use Selenium? And how?
I have something, but as you, I have no time to prepare anything well structured.. see you in Basel :) -- Context is everything: http://forum.magnolia-cms.com/forum/thread.html?threadId=cd353fab-6ab0-474e-8d66-49ef605ba55a ---------------------------------------------------------------- For list details, see http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <user-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------
