SAVITRIBAI PHULE PUNE UNIVERSITY, PUNE

REPORT ON

CROP INFORAMTION
SUBMITTED TO THE SAVITRIBAI PHULE PUNE UNIVERSITY, PUNE
IN THE FULFILLMENT OF THE REQUIREMENT

Of

Laboratory Practice - IV
Final Year (Computer Engineering)
Academic Year 2024-25

BY

Name of Students: Roll No.:

Onkar Vaidya 4202064
Mansi Kale 4202003
Sanika Mandhre 4202017
Ritika Kulkarni 4202013

Under the Guidance of

Mr. N. V. Kamble

DEPARTMENT OF COMPUTER ENGINEERING

STES’S SINHGAD INSTITUTE OF TECHNOLOGY AND SCIENCE
NARHE, PUNE – 411041
 CERTIFICATE

This is to certify that,

Name of Students: Roll No.:

Onkar Vaidya 4202064
Mansi Kale 4202003
Sanika Mandhre 4202017
Ritika Kulkarni 4202013

Studying in BE Computer Engineering Course SEM-VII has successfully completed their LP- IV
Lab Mini-Project work titled “Dynamic website of crop information” at Sinhgad Institute of
Technology and Science, Narhe in the fulfilment of the Bachelor’s Degree in Engineering of
Savitribai Phule Pune University, during the academic year 2024-2025.

Prof. N.V. Kamble Dr. G.S.Navale

Guide Head
Department of Computer Engineering Department of Computer Engineering

Dr. S.D.Markande
Principal

SINHGAD INSTITUTE OF TECHNOLOGY AND SCIENCE, NARHE, PUNE– 411041

Place: Pune

Date:
 Acknowledgement

I take this opportunity to acknowledge each and every one who contributed

towards my work. I express my sincere gratitude towards Prof. N. V. Kamble,

Assistant Professor at Sinhgad Institute of Technology and Science, Narhe , Pune ,

for him valuable inputs , guidance and support throughout the course.

I wish to express my thanks to Dr.G. S. Navale, Head of Computer

Engineering Department, Sinhgad Institute of Technology and Science, Narhe for

giving me all the help and important suggestions all over the Work. I thank all the

teaching staff members, for their indispensable support and priceless suggestions.

I also thank my friends and family for their help in collecting data, without

their help Course report have not been completed. At the end, my special thanks to

Dr. S.D.Markande, Principal Sinhgad Institute of Technology and Science, Narhe

for providing ambience in the college, which motivate us to work.

Name of Students: Sign:

Onkar Vaidya

Mansi Kale

Sanika Mandhare

Ritika Kulkarni
 Contents

PAGE NO
CHAPTER TITLE

1 Introduction 1

2 Objectives 3

3 Testing Strategy 4

4 Hardware & Software Requirement 6

5 Test Schedule 9

6 Result 10

7 Conclusion 17
18
8 References
 1. INTRODUCTION

The crop information application is designed to assist farmers and agricultural professionals in accessing vital
crop data, including growth conditions, pest management, and market prices. The application will be web-
based, allowing for easy access across devices.
Selected System Environment and Platform
• Platform: Web-based application
• Frontend: React.js for dynamic user interface
• Backend: Node.js with Express for server-side logic
• Database: MongoDB for storing crop information and user data
• Hosting: AWS for scalable deployment
Programming Languages
• JavaScript: Used for both frontend and backend development
• HTML/CSS: For structuring and styling the web application
• JSON: For data interchange between client and server
Test Plan
Features to be Tested
1. User Authentication: Registration, login, and password recovery.
2. Crop Information Retrieval: Searching and filtering crop data based on various parameters.
3. Data Submission: Ability to submit new crop data or updates.
4. User Dashboard: Display of personalized crop information and alerts.
5. Responsive Design: Application usability across various devices.
6. Performance: Load times and responsiveness under varying user loads.
Bug Taxonomy
1. Functional Bugs: Issues with feature implementation or unexpected behavior.
2. Usability Bugs: Problems that affect user experience or interface design.
3. Performance Bugs: Slow load times or unresponsive features.
4. Security Bugs: Vulnerabilities in user authentication or data protection.
5. Compatibility Bugs: Issues arising from different browsers or devices.
Test Cases
Test Case 1: User Authentication
• Test Procedure:
5
 1. Navigate to the login page.
2. Enter valid credentials and click "Login."
3. Verify successful login and redirection to the dashboard.
Test Case 2: Crop Information Retrieval
• Test Procedure:
1. Use the search bar to enter a crop name.
2. Select filters (e.g., region, season).
3. Verify that the correct crop information is displayed.
Test Case 3: Data Submission
• Test Procedure:
1. Navigate to the data submission form.
2. Fill in the required fields and submit.
3. Confirm that the data appears in the database.
Testing Strategy
Black-box Testing
• Focus: Functional and usability testing without knowledge of internal code structure.
• Tools: Selenium for automated UI testing; Postman for API testing.
White-box Testing
• Focus: Code coverage and path testing to ensure that all logic branches are executed.
• Tools: Jest for unit testing JavaScript functions; Mocha for integration tests.
Test Reports
Test Pass/Fail Criteria
• Pass: 90% of test cases executed successfully with no critical bugs.
• Fail: Any critical bug or less than 90% pass rate.
Acceptance Judgement
Based on the test results, the application will be considered acceptable if:
• All critical features are functioning as expected.
• No high-severity bugs remain unresolved.
• The application meets performance standards under expected load conditions.

6
 2. OBJECTIVES

1. Provide Comprehensive Crop Data:

o Enable access to detailed information on various crops, including growth conditions, pest
management, and best farming practices.
2. Facilitate User Authentication:
o Implement secure registration, login, and password recovery processes to ensure user data
protection.
3. Enhance Data Retrieval:
o Allow users to efficiently search and filter crop information based on parameters such as
region, season, and type of crop.
4. Enable Data Submission:
o Provide functionalities for users to submit new crop data, edit existing entries, and delete
outdated information.
5. Offer Personalized User Dashboard:
o Create a dashboard that displays relevant crop information, alerts, and weather updates tailored
to user preferences.
6. Ensure Responsive Design:
o Design the application to be fully responsive and usable across various devices (mobile, tablet,
desktop).
7. Implement Performance Monitoring:
o Monitor and optimize application performance to ensure fast load times and responsiveness
under varying user loads.
8. Promote Community Interaction:
o Facilitate forums or discussion boards for users to share knowledge, experiences, and tips
related to crop management.
9. Support Data Analytics:
o Integrate analytics tools to provide insights on market trends, weather impacts, and crop yield
predictions.
10. Enhance User Experience:
o Focus on intuitive navigation and user-friendly interface design to improve overall user
satisfaction and engagement.

7
 3. Testing Strategy

Types of Testing
• Functional Testing:
o Validate that all application features work according to requirements. This includes testing user
authentication, data retrieval, and data submission functionalities.
• Usability Testing:
o Assess the application's ease of use, navigation, and overall user experience through feedback
from actual users.
• Performance Testing:
o Evaluate the application's responsiveness and stability under various load conditions, ensuring
it can handle peak user activity without significant slowdowns.
• Security Testing:
o Identify vulnerabilities in the application to protect against unauthorized access, data breaches,
and other security threats.
• Compatibility Testing:
o Ensure the application performs consistently across different devices, browsers, and operating
systems.
2. Testing Approaches
• Black-box Testing:
o Focus on testing the application’s outputs based on given inputs without knowledge of the
internal code structure. This approach is ideal for functional and usability testing.
• White-box Testing:
o Test the internal workings of the application, including code paths, logic branches, and data
flow. This approach is essential for unit testing and ensuring code quality.
3. Testing Tools
• Selenium:
o Automated testing tool for functional testing of the web interface.
• Postman:
o API testing tool for validating backend services and data retrieval processes.
• Jest:
o JavaScript testing framework for unit tests, particularly for frontend components.
8
 • pytest:
o Python testing framework for backend unit tests and integration tests.
• JMeter:
o Performance testing tool for simulating user loads and measuring response times.
4. Testing Phases
1. Unit Testing:
o Test individual components or functions of the application to ensure they perform as intended.
2. Integration Testing:
o Verify that different modules or services of the application work together seamlessly.
3. System Testing:
o Conduct end-to-end testing of the entire application to ensure all features and functionalities
work together as expected.
4. User Acceptance Testing (UAT):
o Involve real users in testing the application to gather feedback and ensure it meets user needs
and requirements before final deployment.
5. Test Environment Setup
• Development Environment:
o Use a local setup for initial testing of individual components.
• Staging Environment:
o Set up a staging environment that mirrors the production environment for integration and
system testing.
• Production Environment:
o Conduct final tests in the live environment to ensure everything functions correctly after
deployment.
6. Test Documentation
• Test Plans:
o Document the overall testing strategy, objectives, scope, and resources required.
• Test Cases:
o Create detailed test cases for each feature, outlining the test procedure, expected results, and
actual results.
• Bug Reports:
o Track and document any identified bugs, including their severity, status, and steps to reproduce.

9
7. Reporting and Feedback
• Test Reports:
o Generate reports summarizing test results, including pass/fail rates, identified bugs, and
recommendations for improvement.
• Feedback Loops:
o Establish processes for incorporating user feedback and addressing issues promptly, fostering
continuous improvement.

10
 4. Hardware & Software Requirement

Hardware Configuration:

RAM 512MB

HARD DISK 10 GB

PROCESSOR 1.0 GHZ

Server Side:
RAM 1GB

HARD DISK 20GB

PROCESSOR 2.0GHZ

Software Requirement:
Client Side:

WEB BROWSER Google Chrome or any Compatible browser

OPERATING SYSTEM Windows or any equivalent OS

11
Server Side

WEB SERVER APACHE

SERVER SIDE LANGUAGE ReactJS 16 OR ABOVE VERSION

DATABASE SERVER MYSQL

WEB BROWER GOOGLE CHROME OR ANY COMPATIBLE

BROWER

OPERATING SYSTEM WINDOWS OR ANY EQUIVALENT OS

12
 5. Test Schedule

Week Day Testing Phase Activities

Week 1 Day 1 Test Planning Define testing scope,

objectives, and resource
allocation.

Week 1 Day 2 Test Case Development Create test cases

For unit testing and
integration testing

Week 1 Day 3 Unit Testing Test individual

components (e.g., user
authentication,
appointment
scheduling). Conduct
code reviews and fix
issues.
Week 1 Day 4 Unit Testing Continue testing
Individual components

Week 5 Day 5 Integration Testing Test interactions

between integrated
modules. Verify data
flow and functionality
across the system.
Week 1 Day 6 Integration Testing Continue integration
testing

Week 1 Day 7 Integration Testing Finalize integration

testing.

13
 6. Result

Home Page

14
Add Data:

15
Search Data:

16
Delete Data:

17
Test Case:

18
 7. CONCLUSION

In conclusion, the development of the crop information application using React.js 18 promises to
deliver a robust and user-friendly platform for agricultural professionals and farmers. By leveraging
the latest features and enhancements of React, such as automatic batching, concurrent rendering, and
improved data fetching with Suspense, the application will provide a seamless user experience. The
careful integration of testing strategies—including functional, usability, and performance testing—
ensures that the application is reliable and secure. With a focus on user needs and real-time data
access, this application not only empowers users with valuable insights but also fosters a community-
driven approach to agricultural practices, ultimately contributing to enhanced productivity and
informed decision-making in the farming sector.

19
 8. References

React Official Documentation

React. (n.d.). React Documentation. Retrieved from https://reactjs.org/docs/getting-started.html
React Testing Library
Testing Library. (n.d.). Testing Library - React Testing Library. Retrieved from https://testing-
library.com/docs/react-testing-library/intro/
Postman
Postman. (n.d.). Postman Documentation. Retrieved from
https://learning.postman.com/docs/getting-started/introduction/
Jest Documentation
Jest. (n.d.). Jest Documentation. Retrieved from https://jestjs.io/docs/getting-started
Performance Testing with JMeter
Apache JMeter. (n.d.). User Manual. Retrieved from
https://jmeter.apache.org/usermanual/index.html
Agri crop Information Systems
Food and Agriculture Organization (FAO). (n.d.). Digital Agriculture. Retrieved from
http://www.fao.org/digital-agriculture/en/
Best Practices in User Experience Design
Nielsen Norman Group. (n.d.). Usability 101: Introduction to Usability. Retrieved from
https://www.nngroup.com/articles/usability-101-introduction-to-usability/
Crop Management Resources
U.S. Department of Agriculture (USDA). (n.d.). Crop Production and Management. Retrieved
from https://www.usda.gov/topics/farming/crop-production

20