Browse Prior Art Database

A Method for Defining a Reference WebSite to Provide Consistent Testing, Hardened Functionality, and Improved Availability for Volatile Commercial WebSite Environments

IP.com Disclosure Number: IPCOM000201107D
Publication Date: 2010-Nov-08
Document File: 2 page(s) / 22K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method for developers and testers to use a Reference Website to present them with a stable and consistent view into the Website and the ability to develop and exercise a stable set of test scripts.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 2

A Method for Defining a Reference WebSite to Provide Consistent Testing , Hardened Functionality, and Improved Availability for Volatile Commercial WebSite Environments

Commercial websites, especially those supporting eCommerce, undergo frequent changes. These changes may include simple cosmetic changes to content and page layout or changes to add functionality. The accepted method for testing websites involves recording "scripts" recreating a user visit engaging various functions. These scripts represent a significant investment in time to record, parameterize, and develop corresponding data. Often the rate of change in the presentation layer makes it impossible to keep the test scripts current. This limits the ability to do timely regression testing or to assure the site for performance during peak events.

Also, some sites change so rapidly, they often find themselves with functionality that does not work, scale, or perform. Often, the recovery procedures involve failing over to alternative hardware or redeploying code to a known, good baseline. Both are time-intensive, and may impact the end-user experience during the recovery process.

Some websites architect their website interfaces to a consistent framework, using web services or other interface architecture techniques. These consistent interfaces provide a convenient, stable test point. However, many sites have grown organically without defining clean architectural connection points. Also, the interactions at the presentation layer require their own testing.

As a solution, a Reference Website provides a consistent view of the core website functionality. A Reference Website provides a view of essential and proven functionality without incorporating non-essential or higher-risk functions. As the Reference Website experiences a significantly lower rate of change, this also makes it a suitable choice for regression testing (the scripts will not require constant maintenance).

A Reference Website also provides a "first line of defense" in the event of problems. The Reference Website can quickly become the "public" face of the Website if new functionality or presentation layer changes prove problematic. The changes required...