In this post we will discuss about Web Application testing which are useful for Testing. Also you can check out my previous posts on:
- QuickTest Testing Process
- How to do Web Application Testing?
- Cost Of Defect Repair in Testing
Web Application Testing:
Testing which goes beyond the basic functional and system testing of the computer science world, to include tests for availability, performance/load, scalability, usability, compatibility and links.
- Optimize testing with through risk analysis of the site to identify and prioritize key areas and testing asks.
- Consider interaction between HTML pages TCP/IP communications, internet connections, firewalls, and applications that run on the server side.
- Testing ensures that reliability, accuracy and performance of web based applications, including web services.
- Simulate a live application environment if required.Characteristics of Web app Errors:
- Many types of Web App tests uncover problems evidenced on the client side using as specific interface (e.g., may be an error symptom, not the error itself)
- It is hard to determine weather errors are caused by problems with the server, the client, or the network itself.
- Some errors are attributable to problems in the static operating environment and some are attributable to dynamic operating environment.
Testing Web Apps for Errors:
- Web App content model is reviewed to uncover errors.
- Interface model is reviewed to ensure all use cases are accommodated.
- Design model for Web App is reviewed to uncover navigation errors.
- User Interface is tested to uncover presentation errors and / or navigation mechanics problems.
- Selected functional components are unit tested.
- Navigation throughout the architecture is tested.
- Web App is implemented in a variety of different environmental configurations and the compatibility of Web App with each is assessed.
- Security tests are conducted.
- Performance tests are conducted.
Web Testing Process:
- Content testing: tries to uncover content errors.
- Interface testing: exercises interaction mechanisms and validates aesthetic aspects of user interface.
- Navigation testing: makes use of use-cases in the design of the test cases that exercise each usage scenario against the navigation design.
- Component testing: exercises the web app content and functional units.
- Configuration testing: attempts to cover errors traceable to a specific client or server environment.
Testable Web App interface Mechanisms:
- Links(each link is listed and tested)
- Forms(check labels,field navigation,data entry,error checking,data transmission meaningful error messages)
- Client side scripting(black box and compatibility tests)
- Dynamic HTML(Correctness of generated HTML and compatibility tests)
- Client side pop up windows(Proper size and placement of pop up, working controls,consistent with aesthetic appearance of web page)
- CG I Scripts(black box,data integrity, and performance
testing)
- Cookies
- Application specific interface mechanics.
- QuickTest Testing Process
- How to do Web Application Testing?
- Cost Of Defect Repair in Testing
Web Application Testing:
Testing which goes beyond the basic functional and system testing of the computer science world, to include tests for availability, performance/load, scalability, usability, compatibility and links.
- Optimize testing with through risk analysis of the site to identify and prioritize key areas and testing asks.
- Consider interaction between HTML pages TCP/IP communications, internet connections, firewalls, and applications that run on the server side.
- Testing ensures that reliability, accuracy and performance of web based applications, including web services.
- Simulate a live application environment if required.Characteristics of Web app Errors:
- Many types of Web App tests uncover problems evidenced on the client side using as specific interface (e.g., may be an error symptom, not the error itself)
- It is hard to determine weather errors are caused by problems with the server, the client, or the network itself.
- Some errors are attributable to problems in the static operating environment and some are attributable to dynamic operating environment.
Testing Web Apps for Errors:
- Web App content model is reviewed to uncover errors.
- Interface model is reviewed to ensure all use cases are accommodated.
- Design model for Web App is reviewed to uncover navigation errors.
- User Interface is tested to uncover presentation errors and / or navigation mechanics problems.
- Selected functional components are unit tested.
- Navigation throughout the architecture is tested.
- Web App is implemented in a variety of different environmental configurations and the compatibility of Web App with each is assessed.
- Security tests are conducted.
- Performance tests are conducted.
Web Testing Process:
- Content testing: tries to uncover content errors.
- Interface testing: exercises interaction mechanisms and validates aesthetic aspects of user interface.
- Navigation testing: makes use of use-cases in the design of the test cases that exercise each usage scenario against the navigation design.
- Component testing: exercises the web app content and functional units.
- Configuration testing: attempts to cover errors traceable to a specific client or server environment.
Testable Web App interface Mechanisms:
- Links(each link is listed and tested)
- Forms(check labels,field navigation,data entry,error checking,data transmission meaningful error messages)
- Client side scripting(black box and compatibility tests)
- Dynamic HTML(Correctness of generated HTML and compatibility tests)
- Client side pop up windows(Proper size and placement of pop up, working controls,consistent with aesthetic appearance of web page)
- CG I Scripts(black box,data integrity, and performance
testing)
- Cookies
- Application specific interface mechanics.
