Hi Magnolia!
I'm going to implement a sort of testing "standard" procedure to our new
Magnolia-based infrastructure. I'm quite sure it is an OT question, but
I think also this argument can interest others.
I would like to ask you a lot of things, but I will only ask:
1) How do you (automatically) test your modules?
Our idea is to test using TestNG [1] testing suite and Selenium [2]
The environment is the following:
1) Eclipse as IDE
2) Maven as building tool
3) TestNG as testing suite
Inside TestNG test, call Selenium client (Server started from maven
plugin). We use also cargo for launching tomcat and deploy our application.
The only "nebolous" point is how we can deploy a test-capable magnolia
instance inside the container.
We started to think to build a magnoliaAuthor / magnoliaPublic instance
with an already prepared repository (licence inside, module already
installed). But a lot of question came up to my mind:
- should the repository be on SVN?
- is it possible to use a Magnolia CE empty webapp project? And in this
case, is it possible to add customization (EE licence, modules, ...)?
- is it possible to run Integration Test without an Integration Test
Framework (like Continuum / Hudson)?
Any suggestion, thought, idea is really welcome !
-----------------------------------------------------------------------
[1] http://testng.org/doc/index.html
[2] http://seleniumhq.org/
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
