Practical 8 STE
Practical 8 STE
The application uses end-to-end encryption, ensuring the privacy of users' messages.
WhatsApp also supports features such as status updates, media sharing, and backup
options through cloud services. The performance of the application relies heavily on
internet connectivity, device hardware, and the operating system version.
In this test plan, the goal is to analyze and test key functionalities like sending/receiving
messages, notifications, media sharing, calls, and user interface responsiveness. The tests
will also cover error handling, security aspects, and integration with system-level features
like contacts and notifications.
We also aim to test the user interface for responsiveness and usability across various
device types and screen sizes. The application should provide a smooth and intuitive user
experience. Features such as notifications, contact synchronization, and data backup will
be tested.
Moreover, the test will cover integration points such as cloud storage, mobile network
performance, and device-specific functions. The overall goal is to ensure that WhatsApp
functions reliably under normal, heavy, and low bandwidth network conditions.
1
3. Define the Test Criteria:
Entry Criteria: The test team will begin testing once the latest stable build of the
WhatsApp application is deployed in the test environment. The test environment should
have access to devices running iOS and Android with different hardware specifications.
All required tools and resources should be available.
Exit Criteria: Testing will conclude when all major functionalities are verified and the
predefined pass criteria are met. Bugs found during testing should be resolved, retested,
and closed. Any critical bugs that cannot be fixed must be documented and approved for
release.
Success Criteria: The success of the testing will be measured by the number of test cases
passed and the absence of critical issues that hinder functionality. Additionally, the
performance of the app under different network conditions and the user interface
responsiveness will be considered as success factors.
4. Resource Planning:
Resource planning involves determining the personnel, tools, and devices needed for the
testing process. The team will include test engineers, a test manager, and automation
specialists to cover both manual and automated testing. Test engineers will handle
functional and non-functional testing.
Devices required for testing will include smartphones with varying specifications (low-
end, mid-range, and high-end), tablets, and emulators for different OS versions.
Additionally, the team will use automation tools like Appium or Selenium for performing
regression testing.
The project manager will oversee the progress, while testers will be responsible for
writing test cases, executing them, and reporting bugs. Performance monitoring tools and
bug-tracking systems like JIRA will also be crucial resources.
2
5. Plan Test Environment:
The test environment will consist of devices with various OS versions and network
conditions (2G, 3G, 4G, and Wi-Fi) to simulate real-world usage. We will ensure that the
environment mimics different hardware configurations, screen sizes, and memory
capacities.
The application should be tested on emulators and physical devices to cover both low-end
and high-end smartphones. We will also consider battery performance tests to ensure that
WhatsApp does not drain excessive battery life during usage.
Furthermore, mock services will be used to simulate servers for testing the messaging
features, media sharing, and calls. Tools like Charles Proxy may be used to intercept and
monitor network traffic to validate the encryption and data transfer integrity.
Each phase of testing will follow a sprint-like model, with daily standups to ensure timely
completion of test cases. The final phase of testing will focus on regression testing and
ensuring all critical functionalities are bug-free.
The time estimation for each test case will vary, but on average, it is estimated that the
execution time will range between 10-30 minutes per test case. Complex scenarios
involving calls or media sharing may require additional time for validation.
Additionally, a final test report will be shared with the development team and
stakeholders. This report will summarize the test coverage, issues identified, test case
results, and overall status of the application.
3
Test Cases
TC_0 Verify user User 1. Open None Video call Video call Pass
04 can make a logged in chat is is
video call window initiated initiated
2. Click
video call
button
4
TC_0 Verify User 1. Open Image Status is Status is Pass
06 status logged in status tab or text updated updated
update 2. Add a
feature new
status
5
TC_0 Verify User 1. Long Text Message Message Pass
12 message logged in press on messag is is
forwarding a e forwarded forwarded
functionalit message
y 2. Click
forward
3. Select
chat
6
TC_0 Verify user User 1. Open None Privacy Privacy Pass
17 can change logged in settings settings settings
privacy 2. Go to are are
settings privacy changed changed
settings