QN No 1
QN No 1
Aashish Dhakal
Contents
Introduction.................................................................................................................................................2
Objective.....................................................................................................................................................2
Testing Strategy.......................................................................................................................................2
Hardware Requirements..............................................................................................................................4
Software Requirements...............................................................................................................................4
Conclusion...................................................................................................................................................4
1|Page
Introduction
We are given a web applications having following features.
One-to-one messaging
Group Messaging
Private Messaging
Call functionalities (audio, video, and conference calling)
Create Tickets
Create Meeting
Add Reminder
Objective
Our objective is to is to identify the different types of tests that need to be performed for this
application and outline the specific steps required to execute each test.
Testing Strategy
a. Functionality Testing
i. One-to-one Messaging
o First of all, We should try sending and receiving message
between two end users.
o Then we should check if the user is notified after sending
the message.
o We should check if the message is sent, delivered, or
received.
o We should check if the message is received in correct
order.
ii. Group Messaging
o First of all, We should try to create a new group.
o Then We should try to add various participants to the
group.
o Then we should try sending a message to the group.
o We should check if all the group members are notified
about the sent message.
o We should check if the message sent in the group is
received by all the group members.
o We should check if participants can be admin of the
group.
o We should check if admin can remove other participants
from the group.
o We should check if participants can leave the group.
iii. Private Messaging
o First of all, We should try sending a private message to a
specific participant.
2|Page
o We should check if only the private participants can see the
message sent.
iv. Call Functionalities
o First of all, We should try making audio or video call.
o Then we should check if the participants can join or leave
the call.
o We should check if the participants can invite a new
participant to the call.
v. Create Ticket
o First of all, We should try creating a ticket for a specific
purpose.
o Then we should check if the ticket is created with all
the required information.
o Then we should check if the ticket is associated with
the targeted participant.
vi. Create Meeting
o First of all we should try creating meeting on a specific
schedule with specific participants.
o Then we should check if the meeting invitation link is
sent and received successfully.
o We should check if the participants can leave and join
the meeting again.
o We should check if the meeting features work properly
such as audio, video , raising hands etc.
vii. Adding a Reminder
o First of all, We should try adding reminder for a defined
purpose.
o We should check if the reminder notification is sent.
o We should check if the reminder is triggered on
scheduled time.
b. Usability Testing
o First of all, We should check if the user interface is clean and easy to
use.
o We should check if the UI is responsive.
o We should check if the homepage and navigation button works
properly and labelled properly.
c. Compatibility Testing
o We should check if the application can run on different browsers.
o We should check if the UI is clearly defined on various screen sizes.
o We should check if the application can run on different devices.
o We should check if the user interface runs on various platforms.
d. Performance Testing
3|Page
o We should check if the site can handle large numbers of participants
simultaneously.
o We should check the response time and UI smoothness.
o We should check if the site can run on different network conditions.
o We should check if the site can work on minimum hardware and
software requirements.
e. Security Testing
o We should check if the user can get logged in.
o We should check if only the authorized user can get logged in.
Hardware Requirements
o Any phone or computer that can run web based applications
Software Requirements
o Browsers such as chrome, edge, brave.
Conclusion
In this way, we can test the web based application with various features and ensure proper
web experience to our end users.
4|Page