Skip to main content

Posts

Showing posts from August, 2008

Load / Stress Testing of Websites

1. The Importance of Scalability & Load Testing Some very high profile websites have suffered from serious outages and/or performance issues due to the number of people hitting their website. E-commerce sites that spent heavily on advertising but not nearly enough on ensuring the quality or reliability of their service have ended up with poor web-site performance, system downtime and/or serious errors, with the predictable result that customers are being lost. In the case of toysrus.com, its web site couldn't handle the approximately 1000 percent increase in traffic that their advertising campaign generated. Similarly, Encyclopaedia Britannica was unable to keep up with the amount of users during the immediate weeks following their promotion of free access to its online database. The truth is, these problems could probably have been prevented, had adequate load testing taken place. When creating an eCommerce portal, companies will want to know whether their infra...

Classification of Errors by Severity

Often the severity of a software defect can vary even though the software never changes.  The reason being is that a software defect's severity depends on the system in which it runs. For example, the severity of the Pentium's floating-point defect changes from system to system.  On some systems, the severity is small; whereas on other systems, the severity is high.  Another problem (which occurs regularly) is that the definitions of the severity levels (or categories) themselves change depending on the type of system.  For example, a catastrophic defect in a nuclear system means that the fault can result in death or environmental harm; a catastrophic defect in a database system means that the fault can (or did) cause the loss of valuable data.  Therefore, the system itself determines the severity of a defect based on the context for which the defect applies.  The context makes all the difference in how to classify a defect's severity.  I have attach...

Web Testing Checklist

User Interface Testing 1. Site · Easy to use · Instructions are simple and clear. Additionally, test that instructions are · correct (i.e. if you follow each instruction does the expected result · occur? 2. Site map or navigation bar (if provided) · Is the site map is correct? · Does each link on the map actually exist? · Are there links on the site that are not represented on the map? · Is the navigational bar present on every screen? · Is it consistent? · Does each link work on each page? · Is it organized in an intuitive manner? 3. Site Content · Correctness of wording · No overuse of bold text big fonts and blinking (user acceptance testing) · Hyperlinked references are working · Are patterns, background color and pictures distract the user? · Does all images add value to respecti...

Descriptive Programming

What is Descriptive Programming? Whenever QTP records any action on any object of an application, it adds some description on how to recognize that object to a repository of objects called object repository. QTP cannot take action on an object until unless its object description is in the Object Repository. But descriptive programming provides a way to perform action on objects which are not in Object repository. This technique is useful when the application to be tested has not been developed yet but its interface design is available. Object Identification: To identify an object during the play back of the scripts QTP stores some properties which helps QTP to uniquely identify the object on a page. Below screen shots shows an example Object repository: Now to recognize a radio button on a page QTP had added 2 properties the name of the radio button and the html tag for it. The name the left tree view is the logical name given by QTP for the object. This can be changed as per the conve...