If you establish an appropriate infrastructure, you can perform client-side testing on a servlet immediately after you compile it and perform unit testing. Of course, testing early doesn't eliminate the need for later application-wide testing. However, it does improve the overall efficiency of your development process and make the later phases of testing decidedly less painful.

In the busy world of quality assurance and testing, we often as individual testers/quality assurance professionals dig in and do the daily work we need to do and sometimes leave the overall quality measures to those in management positions. As individuals we need to realize that each of us makes an impact on quality, whether we are proactively and consciously doing so or not.

From a large amount of research, this paper presents best practices for website testing.

Testers are often on the critical path for getting a software release out. They must plan carefully in order to minimize the critical path, while still doing a complete job of testing. This schedule pressure is taken to an extreme when a production server must be taken offline in order to deploy the software, and everyone is waiting for the final test results before the system can go live again. Karen Johnson describes her company's carefully planned and orchestrated method for doing a final check of an installed system. Her story is relevant to e-commerce companies as well as IT shops that are under pressure to keep systems updated while minimizing downtime.