...

These tests should be executed at least once per release. The procedure to execute them is described at
Release QA Plan#Manualtestsusingtheintegrationtestswebapp Manual tests using the integration-tests webapp [Internal, Outdated].

To add such manual tests:

• checkout httpclone ssh://svngit@git.magnolia-cms.com/svn/community/bundle/trunk/platform/ce.git
• depending on what needs to be tested, you can do a combination of:
  • add templates in magnolia-integration-tests-fixture-module/src/main/resources/mgnl-files/templates/test/manual
  • declare those templates in magnolia-integration-tests-fixture-module/src/main/resources/info/magnolia/test/config.properties or via info.magnolia.test.SetupStuffForTests.
  • in the template itself, describe what actions need to be performed for the test to be considered successful
  • add a page with this template to the website, under /manual-tests, via magnolia-integration-tests-fixture-module/src/main/resources/info/magnolia/test/website.properties.

please take this into consideration if you find yourself creating many templates that have no purpose other than holding the test description: in the future, the current website.properties file might be specialized (i.e use a custom, simpler, format, instead of the properties import format; additionally, the test description might figure in there instead of the template, especially for tests where templating isn't relevant); if you're in such case, feel free to do so yourself or give us a shout at Greg !

Automated tests

We also have a suite of automated tests. They rely on the same process, but are executed differently:

• since magnolia-integration-tests lies inside the CE bundle project, they are executed every time to bundle is built. This means they're executed on a regular basis by Hudson Jenkins (httphttps://hudsonjenkins.magnolia-cms.com/job/magnolia-bundle_trunk/) and every time we do a release.

...

There are also groovy scripts in magnolia-integration-tests/tests/src/main/:

• Testing of activation [Internal] that activates content and checks for results
• Crawling test [Internal] that requests all the pages and checks for rendering exceptions
• Log crawling test that reads logs and checks for rendering exceptions.

...

All these tests are executed within the context of a single Jetty instance, which is started by the Cargo plugin of Maven.

The current setup deploys two Magnolia instances (: magnolia-test-webapp and magnolia-test-webapp-public, under the /magnoliaTest and /magnoliaTestPublic contexts, respectively) which currently both .
Both are an extension of magnolia-empty-webapp, additionally installing the magnolia-moduletemplating-samples and magnolia-integration-tests-fixture-module, which is containing contains the pages, templates etc created above, which are used for use while executing the tests.

...