Hi Matteo, Here's my input to this discussion:
1) When doing Java development, I would definitely say that integration tests with Jenkins are worth it, and will save you money (Jenkins is very easy to set up, and having nightly builds of everything, seeing where things break early is worth it). If you're only doing website development (not app, not modules) then I would say doing integration tests (Hudson, Jenkins) doesn't make much sense. If you don't have Java code you'd just be retesting magnolia, and that's the job of the folks at magnolia inc. 2) On the other hand, for the website development Selenium Tests could make sense. It's a hard call - I think they will only make sense if your site is heavy on functionality (lots of forms). For a "normal" site, the effort of setting up Selenium tests probably exceeds the benefits you will get from them. In my largest magnolia project, we test the websites "manually" - there is a test team, and one member is dedicated to CMS/Magnolia tests. This person is integrated in the project, attends our weekly meetings, and has in depth knowledge of the project. She manually tests the websites using different browsers and devices, and tests both layout (appearance) and function. One of the biggest challenges I see to automated website testing is moving the content around between different magnolia instances. For automated tests, you have to start with a "well defined" state for the content. Also, you would typically like to test with content that is close to the production content. This means moving content around between instances, restoring an instance to a previous content state, etc... We are still looking for a good method for doing this. Regards from Vienna, Richard -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von Matteo Pelucco (via Magnolia Forums) Gesendet: Freitag, 04. Oktober 2013 17:29 An: Magnolia User List Betreff: [magnolia-user] Testing a Magnolia project Hello everybody! This is not intended to be a I-NEED-HELP message but instead a CALL-FOR-DISCUSSION thread. The topic is clear: I'm working on a Magnolia website project (not app, not modules..). How can I test my work before releasing it? I would like to know how the Magnolia community test their project. Do you perform unit test? If yes, jUnit? TestNG? Launched with Maven? Do you perform integration test? Hudson? Does really this approach save your money? Do you perform website UI testing? Selenium based? How they are launched? How many time do you spend on this kind of test? Do you perform site-crawling POST-release testing? Which services are you using? How do you test Javascript? And HTML5 + CSS / responsiveness? Thanks for sharing your ideas.. 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]> ----------------------------------------------------------------
