Testing Web Applications

The testing of Web-based applications has much in common with the testing of desktop systems: You need to test the usual functionality,configuration, and compatibility, as well as performing all the standard test types. But Web application testing is more difficult because complexities are multiplied by all the distributed system components that interact with the application.

When we see an error in a Web environment, it’s often difficult to pinpoint where the error occurs, and, because the behavior we see or the error message we receive may be the result of errors happening on different parts of the Web system, the error may be difficult to reproduce. So how do we analyze errors within a Web-based system, and what considerations should be made for reproducing such errors?

Read Full article at
http://www.logigear.com/campaigns/testing_web_applications.pdf

1. When we see an error on the client side, we are seeing the symptom of an error—not the error itself..

2. Errors may be environment-dependent and may not appear in different environments.

3. Errors may be in the code or in the configuration.

4. Errors may reside in any of several layers.

5. Examining the two classes of operating environments—static versus dynamic—demands different
approaches.

Read Full article at
http://www.logigear.com/campaigns/testing_web_applications.pdf