1.

Introduction

Loop Habit Tracker is a popular habit tracking application available for Android devices. It
helps users create and track their daily habits, allowing them to set goals and monitor their
progress over time. The app uses a simple and intuitive interface, making it easy to add habits
and mark them as completed. It also provides features such as reminders, streak tracking, and
data visualization to help users stay motivated and accountable for their habits.
The app is suitable for people of different age groups and backgrounds who are motivated
to track and improve their habits.
Key Features of the latest version of the application are:

* Track numeric habits (e.g. how many pages did you read?)
* Skip days without breaking your streak
* Show question marks for days with missing data
* Extend day a few hours past midnight
* Show multiple habits in a single widget
* Export daily backups automatically
* Sort habits by status and in reverse
* Add notes to habits
* Improve theme and accessibility

Pic 1. List of habits Pic 2. Information about habit.

 Pic 3. Habit statistics. Pic 4. Widget.

2. Objectives

The objective of this test plan is to validate the functionality, usability, performance and
compatibility and ensure comprehensive testing effort for the Loop Habit Tracker application.

- Verifying the key features of the Loop Habit Tracker are functioning correctly.
- Assess UI elements and verify user-friendliness.
- Measure the performance and responsiveness under normal and peak load conditions.
- Test application in various Android devices.

2. Scope

The scope of this test plan covers the following components of the Loop Habit Tracker
application:

Component Description
Habit Creation and Tracking Creating new habits with name, description, and schedule
settings. Tracking habit completion and maintaining streaks.
Habit Editing and Deleting Modifying existing habits and Delete from app.
Reminders and Setting reminders for habit tracking
Notifications
Habit Statistics and Progress Viewing habit statistics, such as completion rates, streaks, and
Tracking trends.
User Interface and Evaluating the UI for clarity, intuitiveness, and ease of use.
Navigation
Performance Measuring the app's performance in terms of speed,
responsiveness, and resource consumption.
 3. Test Approach

The testing approach for this project is combination of automated and manual testing. We will
perform various test scenarios and validate the expected behavior of the database system.

4. Test Environment

Hardware:
- Machine or laptop on Windows 11.
- 5GB and more RAM.
- Ryzen 5 and newer.
Software:
- APK 13.
- Appium v.1.22.3
- Apache JMeter v.5.5
- Jira RTM
Network:
- A stable network connection for testing features that rely on internet connectivity,
such as data synchronization, notifications, and remote services integration.
Emulator:
- Pixel 3a API 31

5. Test Requirements.

Requirement Requirement Description Test Cases Executed Test Case

ID Status
T-REQ-001 Functional Testing TC-001, TC-002, TC-004, TC- Passed
006, TC-007, TC-008, TC-009
T-REQ-002 Usability Testing TC-003, TC-016, TC-018 Passed
T-REQ-003 Performance Testing TC-019 Passed
T-REQ-004 Compatibility Testing TC-020, TC-018 Passed
T-REQ-005 Error HandlingTesting TC-010, TC-011, TC-012, TC- Passed
013, TC-014, TC-015
T-REQ-006 Localization and TC-017 Passed
Internationalization Testing

T-REQ-001 – Functional Testing: 1. User creates “Yes or No” Habit. 2. User creates "Measurable" Habit. 3. User
wants to sort the habits 4. User set the reminder. 5. User sets habit in calendar. 6. User modifies the habit. 7. User
exports the habit. 8. User deletes the habit. 9. Change the settings (first day of the week).
T-REQ-002 – Usability Testing: 1. User turns the dark theme. 2. Widen Widget. 3. Switch between portrait and
landscape orientation.
T-REQ-003 - Performance Testing: 1. Load Testing
T-REQ-004 - Compatibility Testing: 1. Change device to simulator. 2. Switch between portrait and landscape
orientation
T-REQ-005 - Error HandlingTesting: 1. Reminder with incorrect time setting. 2. Invalid Habit Creation. 3. Excessive
number of habits. 4. Input SQL commands/special characters. 5. Cross-Site Scripting Attack. 6. Exceed maximum
allowed input length
 6. Test Case

The following template will be used to create test cases:

Test Description Test Data Expected Results

Case
ID
TC001 User creates “Yes or No” Habit Loop Habit Tracker It appears in list
TC002 User creates "Measurable" Habit Loop Habit Tracker It appears in list
TC003 User turns the dark theme Loop Habit Tracker Application response in 5
seconds
TC004 User wants to sort the habits Loop Habit Tracker Successful login
TC005 User set the reminder Loop Habit Tracker Notification is sent at the
time he set the reminder
TC006 User sets habit in calendar Loop Habit Tracker All analytic charts changes
TC007 User modifies the habit Loop Habit Tracker Changes are applied
TC008 User exports the habit Loop Habit tracker Exports in csv format
TC008 User deletes the habit Loop Habit Tracker The verification window
shows up
TC009 Change the settings (first day of the Loop Habit Tracker The week is modified
week)
TC010 Invalid Habit Creation Loop Habit Tracker Gives an error sign
TC011 Reminder with incorrect time setting Loop Habit Tracker Gives an error sign
TC012 Excessive number of habits Loop Habit Tracker Application is stable
TC013 Input SQL commands/special Loop Habit Tracker App sanitizes the input
characters
TC014 Cross-Site Scripting Attack Loop Habit Tracker App sanitizes the input
TC015 Exceed maximum allowed input Loop Habit Tracer Implement Proper input
length
TC016 Widen Widget Loop Habit Tracer Widget takes all empty
space
TC017 Change the language Loop Habit Tracker UI elements translated
TC018 Switch between portrait and Loop Habit Tracker UI elements are stable
landscape orientation
TC019 Load Testing Loop Habit Tracer Works properly
TC020 Change device to simulator Loop Habit Tracer Works properly
Load testing:
Localization and Internationalization Testing:

5. Test Schedule

The test execution for the database testing will be conducted according to the following
schedule:

Test Activity Start Date End Date

Test Plan and Test Cases Creation 9.06.23 10.06.23
Test Environment Setup 10.06.23 11.06.23
Test Execution 11.06.23 13.06.23
Test Reporting and Documentation 13.06.23 14.06.23

6. Test Deliverables

The following deliverables will be produced as part of this testing effort:

1. Test Plan:
Outlining the objectives, scope, approach, and schedule of the database testing. It
provides guidance and instructions for the testing team to follow.
 2. Test Cases:
Detailed test cases that cover various scenarios for validating different components of the
application. Each test case includes test steps, expected results, and any necessary test data.
3. Test Execution:
Reports summarizing the execution of test cases, including the test case ID, description,
pass/fail status, and any issues encountered during the testing process. These reports provide a
clear overview of the testing progress.
4. Defect Logs:
A log of all identified defects or issues discovered during the testing. Each defect should
include details such as a description, severity level, steps to reproduce, and the person
responsible for resolving the defect.
5. Test Report:
A comprehensive report summarizing the entire database testing effort. It includes an
overview of the testing activities, test coverage, test execution results, identified issues,
recommendations for improvement, and a conclusion.

7. Test Dependencies

The successful execution of this test plan depends on the following:

 Availability of test data for different scenarios.

 Access to the test environment with the required database system and
configurations.
 Collaboration with the development team for any necessary changes or bug fixes.