CHAPTER-4

i. Test plan
1. User Interface Testing
 Verify the consistency and correctness of UT design.
 Check the responsiveness of web application to different screen size.
 Validate the consistency of content and images displayed on the
website.
 Verify that website is accessible to all user types and meets web
guidelines.

2. Functionality Testing
 Verify that users can register and login to the application.
 Verify that users can view the list of available food donations.
 Check the functionality of search feature and ensure it is returning the
expected results.
 Verify that users can donate food items to the application.
 Verify that users can claim food items from the application.
 Verify that users can update their profile information.
 Verify that users can contact each other through the application.
 Verify that administrators can manage the food donations and users.
 Verify the checkout process and ensure users receive confirmation
and/or receipt for their donation.
 Test the admin functionality, i.e., managing food items and donations.

3. Performance Testing
 Check the loading time of pages and ensure that pages load quickly.
 Evaluate the applications performance under heavy load and ensure it
can handle multiple users and food donation simultaneously.
 Validate the responsiveness of the application to user actions, such as
searching or donating.
4. Security Testing
 Validate the security of user registration and login process.
 Test the website for vulnerabilities, such as cross-site scripting and
SQL injection.
 Verify that user data and payment information is protected and
encrypted.

5. Usability Testing
 Test the website's usability and ensure that it is easy to use for all user
types.
 Evaluate the application response time and loading speed.
 Evaluate the applications accessibility and responsiveness on different
devices and browsers.
 Evaluate the applications error messages and ensure they are
informative and clear.
 Validate that the website meets user requirements and expectations.
 Gather user feedback and incorporate it into future iterations of the
application.

6. Compatibility Testing
 Test the website on different browsers (Chrome, Firefox, Safari, etc.)
 Verify the website's compatibility with different operating systems
(Windows, Mac, Linux).
 Test the website on different devices (laptops, desktops, tablets, mobile
devices).

7. Localization Testing
 Validate the website's ability to support multiple languages and
cultures.
 Verify that all text is correctly translated and displayed in the correct
language.
 Test the website on different locales (date formats, currency, etc.
ii. Features Tested
1. User Registration and Login
 User registration and login functionality can be tested to ensure that users can
sign up and access the system securely.
 The login functionality can be tested to ensure that users can log in with their
credentials.

2. Food Donation
 The food donation functionality can be tested to ensure that users can donate
food items easily.
 The system should allow users to add food items, including the type of food,
quantity, and expiry date.
 The donation process can be tested to ensure that users can complete the
transaction securely.

3. Food Management
 The food management functionality can be tested to ensure that admins can
manage the donated food items.
 The system should allow admins to view, edit, and delete donated food items.

4. Search Functionality
 The search functionality can be tested to ensure that users can easily search for
food items based on different criteria, such as food type, location, or expiry
date.

5. Payment Gateway Integration

 The payment gateway integration can be tested to ensure that the payment
process is secure and reliable.
 The system should allow users to make payments using different payment
methods, such as credit card, PayPal, or other online payment options.
 6. User Interface
 The user interface can be tested to ensure that the website is easy to use,
visually appealing, and user-friendly.
 The website should be responsive, accessible, and compatible with different
devices and browsers.

7. Performance and Scalability

 The website's performance can be tested to ensure that it loads quickly, even
during peak traffic hours.
 The system's scalability can be tested to ensure that it can handle large
volumes of traffic and donations.

8. Security
 The system's security can be tested to ensure that user data and payment
information are protected and encrypted.
 The website should be tested for vulnerabilities, such as cross-site scripting,
SQL injection, and other security threats.

9. Usability and User Experience

 The website's usability and user experience can be tested to ensure that it
meets user requirements and expectations.
 The system should be intuitive, easy to navigate, and provide users with a
seamless experience.

iii. Features not Tested

1. User-friendliness: The application may not have been tested for its ease of use
and user-friendliness, which can affect user engagement and adoption.
 2. Compatibility: The application may not have been tested for compatibility with
different devices, operating systems, and web browsers, which can result in user
frustration and a loss of potential users.

3. Security: The application may not have been tested for security vulnerabilities, such
as data breaches, hacking attempts, or phishing scams, which can compromise user
data and privacy.

4. Scalability: The application may not have been tested for its ability to handle large
volumes of data and users, which can result in slow performance, system crashes, and
user dissatisfaction.

5. Integration: The application may not have been tested for its ability to integrate
with other systems, such as food banks, charities, and logistics providers, which can
limit its effectiveness in facilitating food donations and reducing food waste.

6. Accessibility: The application may not have been tested for its accessibility to
users with disabilities, such as visual or hearing impairments, which can exclude a
significant portion of the population from using the application.
7. Localization: The application may not have been tested for its localization, such as
language and cultural adaptations, which can limit its reach and effectiveness in
different regions and countries.

iv. Findings
1. There is a significant amount of food waste generated by households, restaurants,
and grocery stores on a daily basis. According to the United Nations,
approximately one-third of all food produced for human consumption is lost or
wasted globally, which translates to about 1.3 billion tons of food per year.
 2. Food waste has negative environmental, economic, and social impacts. It
contributes to greenhouse gas emissions, wastes valuable resources such as water
and energy, and exacerbates food insecurity and poverty.

3. A waste food management and donation web application can help address these
issues by connecting surplus food with organizations and individuals who can use
it, such as food banks, shelters, and charities. These applications can facilitate the
donation process by allowing users to easily post information about available
food, and enabling recipients to easily locate and request donations.

4. There are several waste food management and donation web applications
currently available, including apps like Too Good To Go, OLIO, and Food Cloud,
which have gained popularity in recent years. These apps often rely on a network
of volunteers and partner organizations to facilitate donations.

5. While waste food management and donation web applications can be effective in
reducing food waste and addressing food insecurity, they also face some
challenges. These include issues related to food safety, logistical challenges in
coordinating donations, and difficulties in scaling up the platform to reach a larger
audience.

6. To overcome these challenges, waste food management and donation web

applications need to be designed with careful consideration of food safety
regulations, and should incorporate features to help streamline the donation
process and improve communication between donors and recipients. Additionally,
partnerships with organizations in the food industry and local communities can
help to increase the reach and impact of these applications.

v. Inference
 1. Reduction of Food Waste: A waste food management and donation web
application can help reduce food waste by connecting restaurants, grocery
stores, and individuals with excess food to local charities and non-profits. This
can help ensure that food is not thrown away, but rather used to feed those in
need.

2. Increased Access to Food: By connecting donors with charities and non-

profits, the web application can help increase access to food for those who are
food-insecure. This can help improve the health and well-being of individuals
and families who may not have enough to eat.

3. Sustainability: By reducing food waste, the web application can help promote
sustainability and reduce the environmental impact of food production and
disposal.

4. Efficiency: The web application can help streamline the process of donating
food, making it easier and more efficient for donors and recipients alike.

5. Community Building: A waste food management and donation web

application can help build stronger communities by connecting donors with
local charities and non-profits. This can help foster a sense of social
responsibility and encourage people to take action to address food waste and
hunger.

Overall, a waste food management and donation web application has the potential to
make a positive impact on both individuals and the environment. By reducing food
waste and increasing access to food for those in need, such an application can help
build a more sustainable and equitable society.