The goal of this chapter is to understand the different types of testing required for eZ publish projects. This covers all levels of the end solution, not just what appears on the surface. It includes the following:
Load Testing
Testing, Monitoring, and Reporting Tools
Browser and User Acceptance Testing
Accessibility Testing
In a good project plan, plenty of time is allowed for testing and the test plan should be done after the specification, well before the solution is ready to be tested. In reality, testing time is often sacrificed to meet deadlines; this leads to the release of solutions that contain bugs that need to be fixed once the solution is in a live environment. Although it is rare for a solution to go live without some bugs, it's important to make sure obvious errors are fixed before going live. It's far more expensive and time consuming to fix problems when a solution is in production due to the additional re-testing and re-deployment involved.
Based on the nature...