Hi Matteo, We usually would not have more than 2 developers working on the same templates. Our developers are in the same room, so they can easily communicate. It happens rarely, but sometimes the developers do cause conflicts with each other - but it happens very rarely.
Normally I am a fan of automated tests, but for the template development in magnolia it does not seem worth it to me. At least for us, our customers expect us to be fast with the template development. We need to implement changes within a 1-week timeframe. I don't believe that would give us enough time to write sensible Selenium tests, at least not ones that do more than the basic "check output for a template exception". So we do manual testing, especially since we have the resources (test-team) available for this. Your suggestion for automatic content generation seems sensible, it might be hard to implement though... Regards from Vienna, Richard -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von Matteo Pelucco (via Magnolia Forums) Gesendet: Dienstag, 08. Oktober 2013 11:37 An: Magnolia User List Betreff: [magnolia-user] Re: Testing a Magnolia project Hi Richard, thanks for sharing your methods / ideas. Just to know, how many developers work (avg. spk.) on the same code or on "overlapping" code at the same time? For instance, if devA works on page properties of a section just to add some Google Analytics settings and devB works on the same page properties to add some other javascript functionalities, probably their code should be tested togheter to see if conflicts. But this scenario can be easily extended to a dev team that work independently on a set of components that need to be integrated on the same page in different position. Do you think that even easy Selenium tests could be worthy for situation like that? To Magnolians folks: what about some test to automatically build a site with all the combination of components? You look at template definition.. see what components are enabled for each areas.. create pages, bind templates.. autogenerate component with some mock test / option according to dialog.. here, manual or automatic test with Selenium.. Just a raw though.. Matteo -- 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: <[email protected]> ---------------------------------------------------------------- ---------------------------------------------------------------- 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: <[email protected]> ----------------------------------------------------------------
