Chapter 7: Testing and Feedback
Testing and Feedback
During the development of EduLink, we focused heavily on manual testing to ensure that all features were working smoothly and as expected. Our testing approach was divided into several key phases:
Functional Testing
We manually tested each feature in different usage scenarios, including:
User authentication (sign-up, login, Google sign-in)
Course creation and management by professors
Viewing and interacting with course materials
Posting and replying in the Q&A forum
One-to-one chat functionality between students and professors
Notification delivery and user interface responsiveness
Cross-Device Testing
To ensure accessibility and a consistent experience, the app was tested on different screen sizes and Android versions. This helped identify UI scaling issues and make the interface responsive and user-friendly.
Internal Feedback
We collected continuous feedback from our team members during development. Each member tested features as they were built and provided suggestions for improvement. This feedback loop helped us catch bugs early and improve the user experience iteratively.
Peer & Instructor Feedback
We shared the application with classmates and instructors, who provided valuable input regarding usability and clarity. Some suggestions included:
Making navigation between courses easier
Improving the layout of course materials
Enhancing the visibility of chat and Q&A features
While most core features work reliably, we observed that:
Some delay might occur in updates depending on internet speed, as data syncs with Firebase in real-time.
Certain rare edge cases in user interaction may need additional handling in future versions.
Last updated