Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Most commonly used web browsers are . Internet Explorer Mozila Google Chrome Opera Safari
Mozilla Firefox is the second most popular web browser, which is impressive because it doesn't come pre-installed on any computers (so a full quarter of people separately downloaded it). It is extremely secure .. Because it is a open source, are extremely fast at fixing any security holes they do find. It has support for a huge add-on library that can do anything from make the browser look different to give you the weather to block the ads on web pages.
Google Chrome is Google's web browser, released just over a year ago. It is the fastest browser available now by far and is also extremely secure. It isolates every tab so that no tab can crash the browser. It is gaining add-on support but does not have it yet. It is based on WebKit, which is currently the best as far as standards go. In addition to being used in Chrome, it's also used in Apple Safari as well as forming the basis of Palm's WebOS.
Opera: It is also fast and secure. It is the second fast browser. It is compatible on different Operating system. It has wide area. Safari: It is fast for video thing. Its work on Mac and window operating system. Its a standalone. It is not secure like Mozilla.
Globalization Testing
Globalization is the process of internationalizing the website so that it supports multiple locales and cultures. The process of internationalization ensures that the application is able to process content, referred to in this universal data, for any locale with little or no change to the website. Locale is a combination of both language and cultural environment, including information such as the format of dates, times, currencies, character classification, and sorting rules for strings. Therefore, a goal of internationalization is to separate the locale-dependent content from locale-independent content. Another goal is to use code that is able to process the locale-dependent content. This ensures that the application can be easily localized for a particular culture or locale.
Security Testing
Authentication: The process of establishing the
identity of the user. Authentication can take many forms including but not limited to: passwords, biometrics, radio
frequency identification, etc.
Compatibility Testing
Compatibility of your web site or web application is very important testing aspect on different browser as well as on different OS . Its depend on hardware and software configuration . 1. Browser compatibility 2. OS Compatibility 3. Printing Compatibility
Browser compatibility:. Some applications are very dependent on browsers. Different browsers have different configurations and settings that your web page should be compatible with. Your web site coding should be cross browser platform compatible. If you are using java scripts or AJAX calls for UI functionality, performing security checks or validations then give more stress on browser compatibility testing of your web application. Test web application on different browsers like Internet explorer, Firefox, Netscape navigator, AOL, Safari, Opera browsers with different versions. OS compatibility: Some functionality in your web application is may not be compatible with all operating systems. All new technologies used in web development like graphics designs, interface calls like different APIs may not be available in all Operating Systems. Test your web application on different operating systems like Windows, Unix, MAC, Linux, Solaris with different OS flavors.
Cookie Testing
Cookie is small information stored in text file on users hard drive by web server. This information is later used by web browser to retrieve information from that machine. Two types of Cookies 1) Session cookies: This cookie is active till the browser that invoked the cookie is open. When we close the browser this session cookie gets deleted. Some time session of say 20 minutes can be set to expire the cookie. 2) Persistent cookies: The cookies that are written permanently on user machine and lasts for months or years.
Testing on cookies
1) As a Cookie privacy policy make sure from your design documents that no personal or sensitive data is stored in the cookie. 2) If you have no option than saving sensitive data in cookie make sure data stored in cookie is stored in encrypted format. 3)Delete cookie: Allow site to write the cookies and then close all browsers and manually delete all cookies for web site under test. Access the web pages and check the behavior of the pages. 4) If your web application is using cookies to maintain the logging state of any user then log in to your web application using some username and password. In many cases you can see the logged in user ID parameter directly in browser address bar. Change this parameter to different value say if previous user ID is 100 then make it 101 and press enter. The proper access message should be displayed to user and user should not be able to see other users account.