This is what happens every once in a while. The design and development phase took much longer than originally planned, and when it comes to time to test, the time allocated to test the project is quite small. Web testing is quite different than SQA in the way that a team usually thinks “let’s get it up and running then we’ll fix bugs” afterwards. In most cases after a long and intense development phase it’s actually difficult to get enough motivation to go in and fix bugs right away after the launch of the product. So if you and your team have a very small amount of time to test a Web site, here is a checklist you may want to consider prior to start testing:
+ The functionality that could have the most negative impact on the user experience,
+ The functionality or layout issue that will be the most noticeable by the user,
+ The section of the Web site that the development team sees as risky,
+ The part of the Web site that could affect the image of your client,
+ The browser and OS version used by the target audience,
+ The part of the product that is the most important to the user,
+ What was done in similar situation/projects in the past,
+ The functionality or a section of the web site that can be pushed live post launch.
Archive for September, 2008
Test in Rush Mode
OS and Browser Statistics August 2008
OS Platform Statistics:
Windows XP => 73.9%
Windows Vista => 12.5%
Windows 2000 => 2.4%
Windows 2003 => 1.9%
Windows 98 => 0.2%
Linux => 3.9%
Mac => 4.9%
Browsers Statistics:
IE7 => 26%
E6 => 24.5%
IE5 => 0.1%
Firefox => 43.7%
Mozilla: 0.5%
Safari => 2.6%
Opera => 2.1%
Source: http://www.w3schools.com/