Agrio app Testing Test Plan

Test Plan Identifier

Agrio app Testing TP_1.0

References
Documents that support this test plan include the Project Plan, and Functional Specifications A1
- C5.

Introduction
Agrio provides users with features such as AI-based alert
system in agriculture, recognizes plant diseases and pests, Farm management tool for crop
advisors and Hyperlocal weather forecast. For this case study, we have selected two user
interfaces:
1. Login Screen
2. Fund Transfer Form

Test Items
The system to be tested the frontend customer-facing app which is login and register screen.
These systems should be tested in the latest stable versions of android and Mac.

The systems should be tested on both a Mac machine and Android.

Features To Be Tested
Features to be tested include the following:
● As a user, logging into the app
● As a user, registering into the app
Features Not To Be Tested
Uploading plant problems through a mobile device will not be tested. Only register and login
1functionality will be tested.

Approach
Tests will be executed following the documented test cases stored in Repeato. The test
manager will orchestrate test sessions for each tester. Testers will perform the tests in Repeato,
utilizing its extensive testing capabilities to categorize each case as Pass / Fail / Skip.
Additionally, testers are encouraged to employ Repeato's note-taking features to provide
detailed insights into actual results and any other pertinent information.

Pass/Fail Criteria
All registration and login functionalities of the systems should operate as anticipated and
outlined in the respective test cases. There must be no severe defects detected, and an end-
user should be able to successfully accomplish both registration and login processes. A
minimum of 95% of all test cases should succeed, and no unsuccessful cases should
significantly impede the end-user's ability to utilize the application.

Suspension Criteria
Testing should be paused immediately if either system experiences login issues.

Test Deliverables
Upon completion, the test run results will be saved in Reapeto and the test manager should
then run a report for all completed tests.
Testing Tasks
● Test plan prepared:

- Develop a comprehensive test plan that details the test strategy in detail, describes the
scope and objectives, allocates the necessary resources, defines a well-structured
schedule, and outlines the entry and exit criteria for the test phase. Define complex test
scenarios based on the various functions of the Agrio Plant Health App, covering
aspects such as accuracy of plant monitoring, robustness of disease detection and
effectiveness of the app's recommendation engine. For example, schedule tests for plant
monitoring functions, define scenarios for disease detection and set performance test
goals such as response time benchmark.

● Functional specifications written and delivered to the testing team:

- Engaged in a collaborative effort with the development team to obtain and thoroughly
review complete functional specifications related to the Agrio Plant Health application.
Carefully document any specific requirements associated with plant health monitoring,
data input intricacies, disease identification algorithm intricacies and the nuanced
nature of user interaction in the application. For example, document specific
requirements, such as algorithm accuracy for disease identification, format for data
input and expected output for recommendation features.

● Environment Setup:

- Ensure that the test environment is carefully configured, loaded with relevant and
diverse
test data that accurately reflects the various types of plants and their corresponding
health conditions. Verify seamless configuration of logins and test authorizations,
adapted to different user roles such as crop advisors, farmers and gardeners with
different access levels. Verify the presence and functionality of test payment
information,
ensuring its readiness to test inputs entered by crop advisors, farmers and gardeners.
For example, an environment with multiple plant profiles, configure user roles such as
crop advisor, farmer and gardener to enter the correct input.
 ● Perform the tests.

- Conduct thorough evaluation of application performance across a spectrum of load

conditions, ensuring its ability to efficiently handle concurrent users and process data
with optimal efficiency. Methodically measure response times for critical functionality,
while critically evaluating application scalability under different usage scenarios.
Evaluate app performance under different loading conditions. For example, Simulate
heavy user traffic to assess how the app handles concurrent users and measure
response time for critical functions, ensuring scalability.

● Test summary report:

- Create a comprehensive and in-depth test summary report that outlines and
summarizes
the findings of the test phase. Test findings, any problems or defects found during
testing
and recommendations for additional updates or changes based on test results should all
be included in this report. For example, provide an overview of the test findings, draw
attention to any problems—for example, errors in input and suggest ways to make the
system better. For example, state any serious vulnerabilities found and how they may
affect users.

Environmental Needs
 Test Logins and User Roles:
Configure test logins with different user roles to simulate diverse application users, such
as crop advisors, farmers and gardeners. For example, create test accounts with varying
permissions to ensure application functionality is consistent with different user needs
and responsibilities.

 User Friendly Interface:

 User preferences should guide the design of applications. To make it simple for users to
find solutions for crops, the application has to be user-friendly.

 Performance Testing Environment:

Set up an environment for performance testing to assess the app's scalability and
responsiveness. For example, simulate many concurrent users, especially during peak
usage hours, to assess the app's ability to handle heavy loads and deliver timely
responses.

Responsibilities
 Lead and facilitate testing projects for Agrio Plant Health, ensuring a structured and
organized approach to testing activities and actions to develop and maintain a
comprehensive test plan outlining test strategy, scope and objectives. Coordinate with
development team to understand new features and changes to be tested. Also,
coordinate availability and schedule of testers, ensuring optimal use of resources.
Actions to be taken schedule and organize testing sessions, taking tester availability into
account. Distribute testing tasks based on the expertise and strengths of individual
testers.

Staffing And Training Needs

 For the test phase, two testers will be assigned to evaluate the functionality of three
categories of users, namely crop advisors, farmers and gardeners. In addition, testers
will also test each user register. These testers should have a basic understanding of the
platform, with particular emphasis on user interaction, and clear communication
channels between testers and developers will be established to facilitate efficient issue
resolution throughout the testing process. In addition, regular updates on new features,
changes or improvements in the Agrio Plant Health application. Encourage testers to
stay informed about advances in related Agrio Plant Health technology.
Schedule
 Week 1: Test Planning and Preparation (Start of Testing)

Days 1-2:
Finalize the test plan, including testing objectives, scope, and test scenarios.
Set up the testing environment with relevant data and configurations.
Days 3-5:
Conduct tester training sessions to ensure a clear understanding of the Agrio Plant
Health application.
Review and finalize test cases and test scripts.
Day 6:
Kick-off the first round of testing, focusing on critical functionalities and core features.
Day 7:
Continuing with the first round of testing, addressing initial issues and gathering
feedback.

 Week 2: First Round of Testing

Days 8-11:
Intensively execute test cases, emphasizing comprehensive coverage of all systems and
modules.
Collaborate closely with the development team to address and resolve identified issues
promptly.
Days 12-14:
Conduct daily status meetings to discuss progress, challenges, and potential
adjustments to the testing strategy.
Begin documenting test results and any necessary bug reports.
 Week 3: Bug Fixes and Regression Testing

Days 15-18:
Prioritize and address bugs identified during the first round of testing.
Conduct regression testing after bug fixes to ensure the stability of existing
functionalities.
Days 19-21:
Continue regression testing, focusing on critical paths and high-priority areas.
Collaborate with the development team to verify the effectiveness of bug fixes.

 Week 4: Final Testing and UAT Preparation

Days 22-25:
Initiate the final round of testing, concentrating on end-to-end scenarios and user
acceptance testing (UAT) preparation.
Document and review final test results, ensuring all test cases are executed and all
critical issues are addressed.
Days 26-28:
Conduct UAT preparation activities, including user training sessions if necessary.
Finalize testing documentation, including the test summary report.
Launch Week: UAT and Final Preparations
Days 29-30:
Initiate User Acceptance Testing (UAT) with stakeholders and gather feedback.
Address any last-minute issues identified during UAT.
Day 31:
Finalize the application for launch, ensuring all necessary approvals are obtained.
Conduct a final review of the testing documentation.
Launch Day:
Day 32:
Launch the Agrio Plant Health application as planned.
Risks And Contingencies
 If the first round of testing is not completed within 1 week, it is likely to delay bug fixes
and the final testing phase. Establish a streamlined test schedule with clear milestones
and deadlines. Monitor test progress regularly and identify potential delays early.
Allocate additional resources if necessary, such as additional testing personnel or
equipment, to speed up the testing process.
Approvals

 The Test Manager must review and evaluate the results of the test project, ensure that all
test cases have been executed, and that the established test goals have been achieved. The
Test Manager conducts a comprehensive review of test plans, test cases and test results.
Confirm that all identified issues have been addressed and resolved satisfactorily. Verify
that the testing process adheres to established quality standards and best practices.