Home » 8/1/07 - 9/1/07
Volume Testing !!!


Volume Testing
*****************

 The purpose of Volume Testing is to find weaknesses in the system with respect to its handling of large amounts of data during short time periods. For example, this kind of testing ensures that the system will process data across physical and logical boundaries such as across servers and across disk partitions on one server.

Under: , ,
Usability Testing !!!

Usability:
***********
Correctness is whether the information is truthful or contains misinformation. The accuracy of the information is whether it is without grammatical or spelling errors .Remove relevant information from your site. This may cause misunderstanding or confusion

 General appearance:
* Page appearance
* Color, font and size
* Frames
* Consistent design.

Under: , , ,
Performance and security !!!

Performance
**************
* Connection speed:
1. try with connection speed: 14.4, 28.8, ISDN, Cable, DSL, T1, T#.
2. Time out occurrence.

 * Load:
Check or measure the following
a. What is the estimated number of users per time period and how will it be divided over the period?
b. Will there be peak loads and how will be the system reacts.
c. Can your site handle a large amount of users requesting contain page?
d. Large amount of data from users.

 * Stress:
Check for the following things.
a. Typical areas to test are forms, logins or other information transaction components.
b. Performance of memory, CPU, file handling etc..
c. Error in hardware, software, memory errors (leakage overwrite or printers)

 Security
*********
• Valid and Invalid login.
• Limit defined for the number of tries.
• Verify log files are maintained to store the information for traceability.
• Verify encryption is done correctly if SSL is used.
• No access to edit scripts on the server without authorize

Security Testing
******************
* If your site requires firewalls, encryption, user authentication, financial transactions, or access to databases with sensitive data, you may need to test these and also test your site's overall protection against unauthorized internal or external access.

Under: ,
Client side compatibility !!!

Client side compatibility:
***************************
* platform
Check for the responsibility of
a. Windows (95, 98, 2000 etc)
b. Unix (different sets)
c. Maintosh (if applicable)
d. Linux
e. Solaris
* Browsers
Check for various combinations
a. Internet explorer (3.x, 4.x, 5.x)
b. Netscape navigator (3.x, 4.x, 5.x)
c. AOL
d. Browser settings (security settings, graphics, java etc)
e. Frames and cascade style sheets
f. Applets, ActiveX controls, DHTML, Client side scripting, HTML specification.

 * Printing
Despite the paperless society the web was to introduce, printing is done more than ever considerations on.
a. Text and image alignment.
b. Colors of text, foreground and background
c. Scalability to fit paper size
d. Tables and borders.

Under:
Server side Interfaces !!!

Server side interfaces:
************************

Server interface:
• verify that the communication is done correctly web server, application server, and database server and vice versa
• Compatibility OS server software, hardware, network connections.
• Database compatibility.

Under:
Functionality Testing !!!

Functionality testing:
************************
It is classified as Links, Forms, Cookies, Database

 Links
Internal link, external link, mailto link, Broken link

 Forms
* Field level validation
Check for lenth, special characters, numerical charts etc

 * Final checks
Checking whether the Create, modify, view and delete are working or not.
* Error handling
Check whether appropriate error messages to be displayed.
* Optional and mandatory fields
Mandatory Field should not be left blank and optional field should allow the user to skip the field.

 Cookies
Check whether cookies are enable or not. Websites use cookies to simulate a continuous connection to that site.

 Database
Should not contain wrong or missing data.

Under: , , , ,