Monday, March 1, 2010

Web site Testing

Web site Testing





Compatibility Testing

Ø Compatibility testing tests your web site across a wide variety browser/operating system combinations. This testing typically exposes problems with plug-ins. ActiveX controls, Java applets, JavaScript, forms and frames. Currently there are over 100 possible combinations of different windows operating systems and various versions of NE and IE browsers. It is important to test across a large number of these to ensure that users with diverse config don’t experience problems when using the web site or application.



Content Testing

– Content Testing verifies a web site’s content such as images, clip art and factual text.



Database Testing

– Most web sites of any complexity store and retrieve information from some type of database. Clients often want us to test the connection between their web site and database in order to verify data and display integrity.



Functionality Testing

– Functionality testing ensures that the web site performs as expected. The details of this testing will vary depending on the nature of your web site. Typical examples of this type of testing include link checking, form testing, transaction verification for e-commerce and databases, testing java applets, file upload testing and SSL verification. For testing, which is repetitive in nature, an automated test tool such as Rational’s Visual Test can be used to decrease the overall duration of a test project.



Performance Testing

– Performance Testing measures the web site performance during various conditions. When the conditions include different numbers of concurrent users, we can run performance tests at the same time as stress and load tests.



Eight Second Rule

– Every page within a web site must load in eight seconds or less, even for users on slow modem connections, or they risk losing their user to a competitor site that serves pages more quickly.



Server Side Testing

– Server side testing tests the server side of the site, rather than the client side. Examples of server side testing include testing the interaction between a web and an application server, checking database integrity on the database server itself, verifying that ASP scripts are being executed correctly on the server and determining how well a web site functions when run on different kinds of web servers.



Stress and Load Testing

– Load Testing, a subset of stress testing, verifies that a web site can handle a particular number of concurrent users while maintaining acceptable response times. To perform this type of testing use sophisticated automated testing tools, such as Segue’s SilkPerformer, to generate accurate metrics based on overall system load and server configuration.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.