Java 2EE and XML Development

Скачать в pdf «Java 2EE and XML Development»


system that is fully integrated with your source code control system. If, for example, you use Rational Clear Case for source control, you could implement Rational Clear Quest for defect tracking. Using nonintegrated products for these functions makes the defect resolution process more manual and error-prone, limiting the usefulness of the process and hindering productivity.


On the other hand, when you are using a bare-bones approach such as CVS, the way in which problems are tracked is undefined. Problem tracking using only a source code control system is more often a manual process than an automated one, where developers might be directed to put comments into the commit logs describing the bug they have fixed. If you do not use a version control system at all, tracking modifications to your code base is as ad hoc and error-prone as all your other development activities.

1.3    Testing and deployment in J2EE


J2EE applications are inherently difficult to test and deploy. They are difficult to test because of the levels of indirection in the system and the nature of distributed processing itself. They are difficult to deploy because of the amount of configuration required to connect the various components such that they can collaborate. Difficulty in testing and deployment is the price we pay for the generality and flexibility of J2EE.

1.3.1    Testing J2EE applications


In table 1.5, we summarized the major types of testing typically done on distributed applications. Picking the types of testing your J2EE application needs is the first order of business. Often your client may dictate this information to you. Most forms of testing are usually required in one form or another, with the exception of integration testing for self-contained systems. This section describes the various types of components that require testing and suggests some strategies for doing so.

Скачать в pdf «Java 2EE and XML Development»