Web site Testing
Kindly help me how to test the web site , sample test cases & sample test plan for that
Guidelines for Web site Testing
@ilatesting by which method do u want to test the web-site?Manually or Automated?
Assuming that you want to test it by manual methods I'll provide u some guidelines. See if it is useful for u... otherwise i'll write automated methods next times
During Web-site testing following points should get considered:
Server side interface
client side compatibility
security of website.
Error message for wrong input
Optional and mandatory fields
Testing will be done on the database integrity.
Testing will be done on the client system side, on
the temporary internet files.
Performance testing can be applied to understand the web
site's scalability, or to benchmark the performance in the
environment of third party products such as servers and
middleware for potential purchase.
o Tested over various Networks like Dial up, ISDN etc
o What is the no. of users per time?
o Check for peak loads & how system behaves.
o Large amount of data accessed by user.
o Continuous load
o Performance of memory, cpu, file handling etc.
Usability testing is the process by which the human-
computer interaction characteristics of a system are
measured, and weaknesses are identified for correction.
Usability can be defined as the degree to which a given
piece of software assists the person sitting at the
keyboard to accomplish a task, as opposed to becoming an
additional impediment to such accomplishment. The broad
goal of usable systems is often assessed using several
Ease of learning
Subjective user satisfaction
Server side interface:
In web testing the server side interface should be tested.
This is done by
Verify that communication is done properly.
Compatibility of server with software, hardware, network
and database should be tested.
The client side compatibility is also tested in various
platforms, using various browsers etc.
The primary reason for testing the security of an web is to
identify potential vulnerabilities and subsequently repair
The following types of testing are described in this
Load testing is usually defined as the process of
exercising the system under test by feeding it the largest
tasks it can operate with. Load testing is sometimes called
volume testing, or longevity/endurance testing
Examples of volume testing:
testing a word processor by editing a very large
testing a printer by sending it a very large job
testing a mail server with thousands of users
Stress testing is a form of testing that is used to
determine the stability of a given system or entity. This
is designed to test the software with abnormal situations.
Stress testing attempts to find the limits at which the
system will fail through abnormal quantity or frequency of
Stress testing tries to break the system under test by
overwhelming its resources or by taking resources away from
it (in which case it is sometimes called negative testing).
The main purpose behind this madness is to make sure that
the system fails and recovers gracefully -- this quality is
known as recoverability.
Stress testing does not break the system but instead it
allows observing how the system reacts to failure. Stress
testing observes for the following.
Does it save its state or does it crash suddenly?
Does it just hang and freeze or does it fail
Is it able to recover from the last good state on restart?
A Testing to ensure compatibility of an application or Web
site with different browsers, OS and hardware platforms.
Different versions, configurations, display resolutions,
and Internet connect speeds all can impact the behavior of
the product and introduce costly and embarrassing bugs. We
test for compatibility using real test environments. That
is testing how will the system performs in the particular
software, hardware or network environment. Compatibility
testing can be performed manually or can be driven by an
automated functional or reg The purpose of compatibility
testing is to reveal issues related to the product&#8217;s
interaction ression test suite.with other software as well
as hardware. The product compatibility is evaluated by
first identifying the hardware/software/browser components
that the product is designed to support. Then a
hardware/software/browser matrix is designed that indicates
the configurations on which the product will be tested.
Then, with input from the client, a testing script is
designed that will be sufficient to evaluate compatibility
between the product and the hardware/software/browser
matrix. Finally, the script is executed against the matrix,
and any anomalies are investigated to determine exactly
where the incompatibility lies.
Some typical compatibility tests include testing your
On various client hardware configurations
Using different memory sizes and hard drive space
On various Operating Systems
In different network environments
With different printers and peripherals (i.e. zip
drives, USBs, etc.)
Re: Guidelines for Web site Testing