During testing the websites the following scenarios should
Server side interface
Client side compatibility
In testing the functionality of the web sites the following
should be tested.
 Internal links
 External links
 Mail links
 Broken links
 Field validation
 Functional chart
 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
Performance testing is a rigorous usability evaluation of a
working system under realistic conditions to identify
usability problems and to compare measures such as success
rate, task time and user satisfaction with requirements.
The goal of performance testing is not to find bugs, but to
eliminate bottlenecks and establish a baseline for future
To conduct performance testing is to engage in a carefully
controlled process of measurement and analysis. Ideally,
the software under test is already stable enough so that
this process can proceed smoothly.
A clearly defined set of expectations is essential for
meaningful performance testing.
For example, for a Web application, you need to know at
least two things:
expected load in terms of concurrent users or HTTP
acceptable response time
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 mailboxes
Examples of longevity/endurance testing:
testing a client-server application by running the
client in a loop against the server over an extended period
Goals of load testing:
Expose bugs that do not surface in cursory testing,
such as memory management bugs, memory leaks, buffer
ensure that the application meets the performance baseline
established during Performance testing. This is done by
running regression tests against the application at a
specified maximum load.
Although performance testing and load testing can seen
similar, their goals are different. On one hand,
performance testing uses load testing techniques and tools
for measurement and benchmarking purposes and uses various
load levels whereas load testing operates at a predefined
load level, the highest load that the system can accept
while still functioning properly.
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 products
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.)
In web application test scenarios are
1.check the URL is correct or not
2.check the links are working or not
3.check how many links are availaable in that page
4.check if we click any link that link is correctly working
or not(it means correct page displayed or not)
5.check whether that page is using tables or not
6.check that web applicaion is secured or not
7.check in that application the text is same or not w.r.t
Is This Answer Correct ?
Other Test Cases Interview Questions
There is a web portal that has been tested and working
properly. Now a new module called as the "online shopping
module" had been added. Ther are two search pages , a
normal search and an advanced search page. You are
responsible for only these two modules for testing
1) Write the scope for testing
2)High level test scenarios
3)Test case for one high level test scenario
4) Assumptions while writing the test case
5) Questions that u might need to ask as a QA to test the
NOTE- the requiremnts wont be given. One has to assume the
Please tell me how to test a search page and also please
help me answer the above questions
I am doing project related to Online order Booking.
In this project different products will be there.
The user can order the product to different location by
giving different shipping Addresses.
By selection of Address shipping price will be calculate.
Now the shipping related part they are integrating with
Depending on the From Zip code, To Zip cobe and Quantity
weight the shipping price will be
I want test scenarios to test the shipping part.
I think ASAP u will help me.
My mail id email@example.com
2.6.3 User Interface
Different Polls could be present at different channels,
pages within channels, and at home page. User interface for
Poll will be as described below:
- Beneath poll current result(running status) to be
shown in graphical form(say progressing bar chart) all the
time, in same window as poll.
- Link ""All Polls >>"" to take user to Polls home
page which will have all the active polls with results
- All the polls not older than one month will come
under Active polls category.
- User can take Active open polls, but cannot react
to Active closed polls. Can only view results of active
- No Interactives available for polls - "Add a
- Registered User can take a poll only once, after
that only result is shown to user. To unregistered user it
will be open.
2.6.4 Interfacing/Sourcing Details
- Polls is going to be a separate module, an internal
application, which editor/admin can publish.
- Admin/Editor should be able to publish polls on
separate channels, pages. Assign closure dates.
- Admin/Editor can upload images, change look n feel,
add a brand, link/url to it.
- System to capture user details(screen name/name,
id, email id), do loyalilty points calculation and add to
user loyality points.
2.6.5 Rules and Conditions
Unless assigned a closure date, by default all Polls will
be open for 30 days.
this is the SRS how to write the test cases for the above
functionalities help me