Testing Web Applications
What is the main difference between testing Cient server application and Web Applications ? Well Client Server application can be 2 tier and Wbe applications are generally 3 tier. Applications on web need to be subjected to more rigorous security, performance and interoperability tests compared to Client server applications.
The tests performed on web applications include:
- - User interface testing
- - Functionality testing
- - Security testing
- - Browser compatibility testing
- - Load / stress testing
- - Interoperability testing/intersystem testing
- - Storage and data volume testing
When testing web applications you will need to tests with following scenarios
- Application running on two or more machines
- Online vs Offline testing.
- High number of concurrent users
- URL testing
- Hardware compatibility, browser compatibility, version compatibility, security issues, performance issues etc.
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?
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.