Web Application Testing

Web Application Testing: Test a Web Based Application , in Web Testing We Consider Many Testing.Web Testing We Test Each and Every Aspect.

http://testingsolution.blogspot.com/2006/12/web-testing-challenges.html

• Short release cycle
• Constantly Changing Technology
• Possibility Of huge number of users
• Inability to control user’s running environment
• 24hour availability of the website

Functionality Testing: It involves making sure that all the features that most affect the user interactions works properly.

• These features may include
• Forms in the page .
• Searches present in the page.
• Pop-up windows (client side and server side) .
• Any online transactions available.

Usability Testing:

• Identify the websites purpose.
• Identify the intended users.
• Whether the user completes the task successfully.
• How much time the user needs to complete the task.
• Number of pages accessed to complete the task.
• At which place in the application the user can .
• possibly make mistakes.
• How the user seeks assistance when lost.
• Whether the online information provides enough help.
• How possibly a user can react for the specific
• download time of the page.
• Point at which the user gets confused and even fail to complete a task.
• Number of clicks between tasks, number of seconds between clicks as well as number of clicks, as well as number of pages browsed.
• Whether the user felt successful in using site.
• Feedback on navigation and other features of the sites.
• Whether the user would recommend this product to friends.
• Whether the user understood the terminology.
• Ideas for improvement
• What the user liked or disliked about the website, and why.

Navigation Testing :

• Ø Easy and quick access to the information.
• Ø Logical hierarchy of the pages.
• Ø Conformation of the page to tell the user about where they are at any point.
• Ø Facility to return to previous state or the home page.
• Ø Consistent look and lay out of every page.
• Ø Moving to and from pages .
• Ø Scrolling through the pages .
• Ø Clicking on images and thumbnails to make sure they work.
• Ø Testing all the links (both internal and external) .
• Ø Ensuring no broken links exists.
• Ø Proper lay out under different browsers.
• Ø Measuring load time of every page.
• Ø Compatibility and usage of buttons, key board shortcuts and mouse actions.

Form Testing:

• Ø Using tab key the form traverses fields in the proper order, both forward and backward.
• Ø Testing boundary values for the data input.
• Ø Checking that the form is capable of trapping invalid data correctly. (Specially date and numeric formats)
• Ø The form is capable of updating the information correctly.
• Ø Tool tip text messages displayed for the form are proper and not misleading.
• Ø Objects are aligned in the form properly, and the labels displayed are not misleading.

Page Content Testing :

• Ø All the images and the graphics are displayed correctly.
• Ø All contents are present as per the requirements.
• Ø Page structures are consistent across the browsers.
• Ø Critical pages contain same contents across browsers.
• Ø All parts of the table or form are present in the right place and in the right order.
• Ø Links to the relevant contents inside or out of the page are appropriate.
• Ø Web pages are visually appealing.
• Ø Checking the vital information’s present in the page are not changing across different builds.

Configuration and Compatibility Testing:

• ØIs the user behind firewall?
• ØDoes the user connect to the application server through a load balance.
• ØDoes the browser accepts cookies?
• ØAre high security settings enabled?
• ØWhat technologies are the developers of the WebPages using?
• ØAre secure blocking tools being used?

Performance Testing:

• ØHigh activity volume at launch.
• ØTime of day .
• ØActivity spikes due to marketing promotions .
• ØBottleneck due to hundreds of users on a network.
• ØDownload time .
• ØUsage patterns .
• ØThink time .
• ØUser arrival rates .
• ØClient platforms .
• ØInternet access speed .
• ØAbandonment rates .

Load Testing:

• Strategy:
• •Understand the load requirements
• •Number of user hits per day/week/month
• •Total concurrent users (worst-case scenario)
• •Peak request rates (Number of pages served per second)
• •Identify the tools and their limitations.
• •Generate enough users and transactions to access capacity.
• •Create a base line criterion.
• •Check the system behavior in multiple sessions.
• •Identify any other application probably running on the client
• •system or server.
• •Execute the test multiple times.

Security Testing:

• ØWhat precautions exist to prevent or limit attacks from users?
• ØAre the browser settings set to ensure maximum security protections?
• ØHow does the website handle access rights?
• ØDoes the application has a virus detection mechanism?
• ØDoes the application handle transaction tempering?
• ØDoes the e-commerce vendor provide a mechanism to prevent
• Øcredit card frauds?
• ØHow does the website encrypt data transfer mechanism?
• ØHow does the web site authenticate users?
• ØDoes viewing the source code disclose any vital information?
• ØHow safe is the credit card or user information?
• ØDoes the application allow for a file to be digitally signed?