The JBoss Development Process Guide tests section
Define what is subject to be tested in the portal and how efficiently testing can be done. We need also to define what tools we will need to use or build for the whole testsuite.
Put in place the integration test with respect to the application server
Put in place the testing infrastructure and configure or build the tools needed for that.
Develop the testsuite.
What we can test
For each module we can define
Web app instrumentation
Servlet and filter commands
JSR 168 tests : Points covered by the TCK and also cover everything that is not tested by the TCK as defined by the portlet specification
Vendor features (PortletSession replication)
Security store that uses JBoss Cache
Test Command Framework: add/delete/move/copy/update nodes and version nodes.
Test HA CMS.
Test jBPM CMS workflow (if exists)
Test RDBMS compatibility.
Test CMS Cache
Layout and Theme framework
RenderSet and Layout Strategy Deployer
Theme and Layout Service implementations
Maximizing Layout Strategy
emptyRenderer and divRenderer renderSets
Get the WSRP TCK running and evaluate it as far as functional coverage goes.
If the TCK cannot be easily run, test each entry point (method) of each WS end points. This will involve creating a SOAP client infrastructure and a set of test clients for each end point. Ideally, this will be achieved outside the container.
Test integration with portal architecture.
What we need
Integration with qa labs
Provide a contract between the layer that runs the tests and the test bed itself
Database contract that defines how we can setup the tests against a defined collection of datasources
Deployment contract that defines how the test bed can manage deployment in the application server
Tools we need
JBoss JCA and TM support for offline tests
Can we test JSF applications ?