| Lesson 9 || Testing the Web site |
| Objective || Describe the Web site elements and applications that should be tested. |
Testing is a continuous process. Your list of items to be tested will be particular to each site. However, server and client components should always be tested, especially the functioning of links, the site display on different browsers, and site performance.
Make a systematic check of all the links on all your Web pages. This check should be made on a regular schedule. There is nothing more annoying to visitors than broken or dead links.
As the Web site develops, the code should be tested in different browsers, different versions of the browsers, and on different platforms.
A Web page may display one way in a particular version of a browser on a certain platform, but may display differently in a later version of the same browser on the same platform.
On a different platform, the page may not be displayed at all. You will learn how to test your code in the SlideShow below.
Test the database to ensure information can be retrieved and manipulated. Try performing queries on the information.
After the Web site is launched, test the pages to see whether downloading and response times are acceptable. Unexpected long delays may require design or code modifications to improve performance.
Test the performance at various times of day, with as many connection types as possible; for example, modems of different speeds, xDSL connections, and so on.
Test to determine how many users the site can handle without crashing.
Routinely test local and remote accessibility to ensure the system is always online.
When new components are added to an existing Web site or application, previously tested functionality should be retested to ensure the new components do not corrupt the system.
This form of testing is called regression testing.
The next lesson wraps-up this module.