/
Testing

Testing

Sept 22, 2017

Prio 1 Unit tests

done

  • By using class design with dependency injection unit tests should be possible using mocking only without further infra structure

Prio 1 Component tests

done by:

  • For component tests stubs are required with in-memory dummy implementations of certain OSGi, JCR, Sling and WCM features, including JSON mount of JCR data

  • Sling and Jackrabbit has implemented such stubs as well, before migrating our stubs we should analyze them and use them if possible

  • Otherwise we need to implement our own stub environment for Sling/WCM-based component tests

Prio 2 Integration tests

open

  • For Sling-based integration tests Sling already provides a good infrastructure which can be run automatically from a maven project - it uses a real sling instance against which the integation tests are run

  • For AEM-based integration tests we have to check what Adobe provides - or develop a similar environment as used by sling ourselves. Or use an external CQ instanze to deploy the integration tests and run them remotely - and make sure all is cleaned up again after the tests are finished (complete or incomplete).

Prio 2 Acceptance / UI tests

Hobbes is much more mature now and hopefully open-sourced in the future. For Selenium & Galen we have http://qa.wcm.io/galenium/

  • Acceptance tests are run using selenium or comparable tools using a browser as frontend

    • Evaluate the "Hobbes" framework which is integrated in CQ6 and the Touch UI as acceptance test framework

  • We have to check if we need generic features that is shared across projects

  • On feature is overriding configuration options from the remove test scripts during a test run - a proposal based on HTTP header injection is described in Testing

Prio 2 Health check tests

obsolete - now https://sling.apache.org/documentation/bundles/sling-health-check-tool.html is available

  • Health check tests are unit tests that are deployed with the applications and are integrated with the Sling health check infrastructure

  • This is intended to be run regularly while the application is running to monitor its status

  • Status is available in the Touch UI Admin console as well

Prio 2 Deployment smoke tests

open - planned as part of ansible roles in https://github.com/wcm-io-devops

  • After each deployment a set of smoke tests should be run to make sure the basic features of the infrastructure and application is running

  • Check that all relevant bundles are deployed in the correct version and running

  • Ensure that cache is cleared

  • Execute a configured set of URLs and check response status