Your application has finally been tested and deployed in a production
environment. However, the IT operators are complaining that the application
is consuming more system resources than originally expected. The problem
being described by the IT operators cannot be repeated in the development
environment. To establish the cause of these problems, it's important to get
enough information about the runtime environment, more specifically what is
going on inside the Java Virtual Machine (JVM).
Before J2SE 5.0, the information available from the JVM was at best extremely
limited. JSR 174 has added management and monitoring APIs in J2SE 5.0 that
expose valuable JVM information. The exposed information ranges from JVM
health indicators like memory and threads to class loading and garbage
collection information. This article provides an introduction to
manageability and des... (more)
Graphical user interface (GUI) testing is a potentially problematic area
because constructing effective test cases is more difficult than the
corresponding application logic. The roadblocks to effective functional GUI
testing are:
Traditional test coverage criteria like "80% coverage of the lines of code"
may not be sufficient to trap all the user interaction scenarios. End users
often use a different user task interaction model than the one conceived by
the development team.
Functional GUI testing needs to deal with GUI events as well as the effects
of the underlying applicati... (more)