Testing

Testing is a process of executing a program or application with the intent of finding

the bugs.
It can also be stated as the process of validating and verifying that a software
program or application or product:
Meets the business and technical requirements that guided its design and

development
Works as expected
Can be implemented with the same characteristic.
Testing is very important because of the following reasons:
1. Software testing is really required to point out the defects and errors that
were made during the development phases.
2. Its essential since it makes sure of the Customers reliability and their
satisfaction in the application.
3. It is very important to ensure the Quality of the product. Quality product
delivered to the customers helps in gaining their confidence.
4. Testing is necessary in order to provide the facilities to the customers like
the delivery of high quality product or software application which requires
lower maintenance cost and hence results into more accurate, consistent and
reliable results.
5. Testing is required for an effective performance of software application or
product.
6. Its important to ensure that the application should not result into anyfailures
because it can be very expensive in the future or in the later stages of the
development.
7. Its required to stay in the business.
Unit Testing:
Unit testing is a software development process in which the smallest testable parts
of an application, called units, are individually and independently scrutinized for

proper operation. Unit testing is often automated but it can also be done manually.
This testing mode is a component of Extreme Programming (XP), a pragmatic
method of software development that takes a meticulous approach to building a
product by means of continual testing and revision.
Sr.
No

Test Plan

Test cases

Expected Result

Sign Up Page

Alert
should
displaying
Required field

Sign Up Page

Login Page

User does enter

any of the details
required
for
Signing Up for
the website
User enter email
with
incorrect
format (missing
@)
User does not
enter username

Login page

User does not

enter password

Adding
Products
the cart

Verification of
user
while
signing up.
Verification of
user
while
signing up.
Login

Cart

the
to

User
putting
Invalid quantity
(negative
or
greater
than
available
quantity)
User
enters
wrong otp.
User
enters
correct otp.
User tries to
login but not
Verified(Otp not
verified)
User clicks on
Remove.

Actual Result
appear
message

Alerts appears displaying

message Please fill out
this Field

Alert
should
appear
displaying message Invalid
Email

Alerts should appear

displaying
message
Invalid Email missing@

Alerts
should
displaying
Required field

appear
message

Alerts should appear

displaying
message
Please fill out this field

Alerts
should
appear
displaying
message
Required field
Alerts
should
appear
displaying message Invalid
quantity, add valid quantity
.

Alerts appears displaying

message Please fill out
this Field
Alerts appears displaying
message Value must be
less than equal to 1 or
quantity available

Message should appear

Invalid Otp try again!!.

Message
appears
Invalid Otp try again!!.

Alert
should
appear
Successfully Signed Up.Now
Login.
Alert should appear Failed
to Login,you may not be
verified, sign in again.

Alert
appears
Successfully
Signed
Up.Now Login.
Alert appears Failed to
Login,you may not be
verified, sign in again.

The specific product should

be removed from the cart.

The specific product is

removed from the cart.

10

11

Reflecting
products
in
cart
added
during
not
Logged-in
state
24x7 Support

12

Cart

User logins to for

proceeding
to
buy
added
products.

The
products
added
previously
should
be
reflected in user cart.

The products added

previously
reflects in
user cart.

User clicks on
24x7 support.
There is no item
in cart.

Call,Mail and Address should

appear.
Buy Now button should not
appear.

Call,Mail and Address

appears.
Buy Now button does
not appear.

Integration Testing: Integration Testing is the phase in software testing in which

individual software modules are combined and tested as a group. It occurs after unit
testing and before validation testing. Integration testing takes as its input modules that
have been unit tested, groups them in larger aggregates, applies tests defined in an
integration test plan to those aggregates, and delivers as its output the integrated
system ready for system testing.

Sr.
No

Test Plan

Test cases

Expected Result

Actual Result

Forgot
password

User clicks on the

forgot
password
button

Forgot password form

should be displayed on
the screen

Cart

User clicks on add to

cart.

Product
Updation

User gives delivery

address and confirms
order

The specific product

should be added to the
cart with the quantity as
specified in the Quantity
tab.
The quantity of the
products bought by the
users must be updated

A form is displayed on
the screen which accepts
the users email address
whose password he
wants to reset
The specific product is
added to the cart with
the quantity as specified
in the Quantity tab.

Product
Addition

User adds to cart a

quantity of a product
greater than the
available quantity

Should not allow the

user to add and display
alert

Sign Up

An already signed up
user tries to sign up

Should not allow to sign

up

After the user checks out

and bill is displayed the
total
no
quantity
available of the bought
products is updated
A message is displayed
than value cannot be
greater than value max
available quantity(max
value displayed)
An alert is displayed that
the user is already

Buy Now

Cart

An
Unregistered
User tries to buy the
cart
After a user logs in

The website should

prompt the user to Log
In
The product in the cart
of the unregistered user
should reflect in the cart
of the registered user as
he logs in

present Please login and

the user is redirected to
home page
The User is redirected to
the login page
The
Cart
of
the
unregistered user is
updated to the cart of
the user that logs in with
previously
added
products also present

System Testing:
System testing of software or hardware is testing conducted on a complete,
integrated system to evaluate the system's compliance with its specified
requirements. System testing falls within the scope of black-box testing, and as
such, should require no knowledge of the inner design of the code or logic.
As a rule, system testing takes, as its input, all of the "integrated" software
components that have passed integration testing and also the software system itself
integrated with any applicable hardware system(s). The purpose of integration
testing is to detect any inconsistencies between the software units that are
integrated together (called assemblages) or between any of the assemblages and
the hardware. System testing is a more limited type of testing; it seeks to detect
defects both within the "inter-assemblages" and also within the system as a whole.

Sr.
No

Test
Plan

Test cases

Expected Result

Actual Result

Login

Display of login page

when user is not in
session

Home
Page

Display of categories and

websites subscribed in
the navigation bar

The user should directly

be redirected to the
Home Page if the logged
in session of the user is
still active
The user should be able
to see all the categories
and websites he/she has
subscribed
in
the
navigation bar

The user is directly be

redirected to the Home
Page if the logged in
session of the user is still
active
The
navigation
bar
displays
a
list of
categories which when
clicked will display the

Navigation
Bar

Home
Page

Home
Page

User moves the cursor to

left side of viewport OR
clicks on the button on
the top-left corner
Display of feeds

Updation of feeds

The
navigation
bar
should slide in view

The user should be

presented
with
all
subscribed feeds with
images
User should be able to
view updated feeds as
soon as the website
updates its rss

websites to which the

user is subscribed
The navigation bar slides
in view

Some
feeds
are
displayed with images
and some are not
The user is able to view
updated feeds as per the
time of update set by the
developer

Link Testing: Link test is to test a group of unit to ensure that the unit operate

correctly in combination. It is normally performed after the individual unit have been
tested in isolation and prior to the integration testing that is performed for the complete
system.

Sr.
No

Test
Plan

Test cases

Expected Result

Actual Result

Logout

User clicks on logout

button in the navigation
bar

User is directed to the

signup page

Explore

User clicks on any of the

provided categories

Home
Page

User clicks any of the

subscribed
websites
provided
in
the
navigation bar

Home
Page

User clicks on Organize

option
from
the
navigation bar

User should be directed

to the login page along
with
a
Logout
successful message
The user should be
redirected to a page
which
displays
unsubscribed websites
of the specified category
The user should be
redirected to a page that
contains the feeds of
only
the
selected
website
The user should be
redirected to a page that
displays all the websites
to which he/she has
subscribed with option
to remove a particular
websites subscription

The user is redirected to

a page which displays
unsubscribed websites of
the specified category
The user is redirected to
a page that contains the
feeds of only the
selected website
The user is redirected to
a page that displays all
the websites to which
he/she has subscribed
with option to remove a
particular
websites
subscription

Log In

User logs in for the first

time

A page containing the

categories to which the
user can subscribe must
be displayed

A page containing the

categories to which the
user can subscribe is
displayed

Browser Testing: Browser Testing is a process to test web applications across

multiple browsers. Browser testing involves checking compatibility of your application

across multiple web browsers and ensures that your web application works correctly
across different web browsers. Browser testing involves testing both the client side and
server side behavior of your Web application when it is accessed using different Web
browsers.

Sr.
No

Test
Plan

Test cases

Expected Result

Actual Result

Mozilla
Firefox
Microsoft
Edge

Entire Website

Should work properly

Works properly

Entire Website

Should work properly

Google
Chrome
Opera

Entire Website

Should work properly

A distortion appears for

the first image on the
signup page
Works properly

Entire Website

Should work properly

Works Properly

3
4