1) Test Plan ID:

TP_001

2) Introduction:
Describe the purpose of the Plan, possibly identifying the level of the plan
(System Test Plan etc.). This is essentially the executive summary part of the plan.It is
System Test Plan for Fruit Disease Detection Using Image Processing,Android
application.In this propose system (Application) ,fruit disease detection system using
image processing is to accurately and efficiently identify and classify diseases or
abnormalities in fruits by analyzing their images. This system can aid in early detection,
monitoring, and prevention of diseases, helping farmers and agricultural experts to take
necessary actions promptly and effectively.The aim is to develop an efficient, accurate,
and user-friendly system that can help in early detection of fruit diseases.

3) Test Items:
1) Login
2) DataSet collection
3) Input Dataset
4) Data Preprocessing
5) Testing Phase
6) Training Phase
7) Split Dataset
8) Feature Extraction
9) Classification Algorithm
10) Apply CNN Model
11) Apply GLCM Model
12) Predictive Model
13) Input trained model
14) Provide Output
15) Detect
16) Detect Disease
17) Disease Detection
18) Solution to disease
4) References:
1. Requirements
2. Project Plan
3. Test Strategy
4. Use cases
5) Features to be Tested:
NO MODULE NAME APPLICATION ROLE DISCRIPTION
1 Open Verify to open application on the device. Open application.
Application
2 Login Verify the functionality of Login button. Click on Login Button.
3 DataSet Verify the functionality of collection Click on collection
collection button. Button.
4 Input Dataset Verify the functionality of Input button. Click on Input Button.
5 Data Verify the functionality of Preprocessing Click on Preprocessing
Preprocessing button. Button.
6 Testing Phase Verify the functionality of Testing Click on Testing button.
button.
7 Training Phase Verify the functionality of Training Click on Training button.
button.
8 Split Dataset Verify the functionality of Split button Click on Split button.
9 Feature Verify the functionality of Extraction Click on Extraction
Extraction button button.
10 Classification Verify the functionality of Classification Click on Classification
Algorithm button. button.
11 Apply CNN Verify the functionality of Apply button. Click on Apply button.
Model
12 Apply GLCM Verify the functionality of Apply button Click on Apply button.
Model
13 Predictive Model Verify the functionality of Predictive Click on Predictive
button button.
14 Input trained Verify the functionality of Input button Click on Input button.
model
15 Detect Verify the functionality of Detect button Click on Detect button.
16 Detect Disease Verify the functionality of Detect button Click on Detect button.
17 Disease Verify the functionality of Detect button Click on Detect button.
Detection
18 Solution to Verify the functionality of Solution Click on Solution button.
disease button
19 Provide Output Verify the functionality of Provide button Click on Provide button.
 6) Features not to be Tested:
These feature are not be tested because they are not included in the software
requirement specs
- User Interfaces
- Hardware Interfaces
- Software Interfaces
- Database logical
- Communications Interfaces
- Website Security and Performance
7) Entry Criteria:
a) Test Design
Team formation, Responsibilities, Schedule,
Requirements, Test Case Template etc…

b) Test Execution:
Readiness of Test Lab
Readiness of AUT
Requirements
Test Case docs
Test Data
Defect Report Template
Etc…

8) Exit Criteria
Specifies the criteria that denote a successful completion of a test phase
- Run rate is mandatory to be 100% unless a clear reason is given.
- Pass rate is 80%, achieving the pass rate is mandatory.

9) Suspension Criteria
If the team members report that there are 40% of test cases failed, suspend testing until the
development team fixes all the failed cases.

10) Roles & Responsibilities

SNO NAME ROLE RESPONSIBILITIES REMARKS

 Group Member Test Planning, guidance, Monitoring and Test
1 Test Lead
Name control
Group Member
2 Sr. Tester Test Data Collection, Generating Test Scenarios.
Name
Group Member
Name Test Case Documentation, Test execution, defect
3 Tester
reporting and tracking for Admin module.

Group Member Test Case Documentation, Test execution, defect

4 Name Tester reporting and tracking for Personal Banking
module.
Group Member Test Case Documentation, Test execution, defect
5 Name Tester reporting and tracking for Corporate Banking
module.

11) Schedule:
SNO TASK DAYS DURATION REMARKS
1 Domain Selection 3 days Date
2 Paper Selection 1 day Date
3 Requirement Gathering 7 days Date
4 Literature Survey 4 days Date
5 Problem Identification 4 days Date
6 Original Architecture 3 days Date
7 Modified Architecture 3 days Date
8 Original Algorithm 4 days Date
9 Modified Algorithm 6 days Date
10 Mathematical Model 2 days Date
11 Analysis 2 days Date
12 Planning 3 days Date
13 Design 30 days Date
14 Coding 30 days Date
Testing 15 days Date
15
Unit Testing
16 Integration Testing 15 days Date
17 White box Testing 15 days Date
 18 Black Box testing 15 days Date

Note: Regression Testing depends on Application and strength of Development team.

12) Test Environment / Lab:

a. Processor - Pentium IV/Intel I3 core
b. Speed - 1.1 GHz
c. RAM - 2 MB (min)
d. Hard Disk - 20GB
e. Keyboard - Standard Keyboard
f. Mouse - Two or Three Button Mouse
g. Monitor - LCD/LED Monitor
h. Smart Phone
i. Operating System:Windows XP and later versions
j. Front & Back End:XML,
k. Programming Language: Android
l. Back end - Java
m. Domain:Image Processing
n. Algorithm: GLCM,CNN
o. Library: OpenCV
p. Database: Firebase/Mysql
q. IDE version: Android Studio 2.3
r. Software Version - JDK 1.7 or above
s. Tools – Eclipse

15) Test Deliverables:

Test deliverables are provided as below
 Before testing phase
- Test plans document.
- Test cases documents
- Test Design specifications.

 During the testing

- Test Tool
- Simulators.
- Test Data
- Test Trace-ability Matrix
- Error logs and execution logs.

 After the testing cycles is over

 - Test Results/reports
- Defect Report
- Installation/ Test procedures guidelines
- Release notes

16) Approvals
SNO TASK/S AUTHOR /ROLE DATE & SIGNATURE

1) Test Plan Documentation Name (Test Lead)

2) Review Name (QA Analist)

3) Approval Name (Project Manager)

17) Glossary:
 AUT -Application Under Test

 SRS- Software Requirements Specification