CST 462S Final Week
Service Learning Project
Throughout CST 462S I performed QA for LibreOffice. This involved reviewing user reported bugs, attempting to reproduce the bugs in LibreOffice, asking for additional information if needed, and updating the status of the bug when applicable.
The project was a good experience overall. Before starting the project I was unfamiliar with QA. Both the site itself and my supervisor provided plenty of resources that helped prepare me for performing QA. After having finished the project I feel much more comfortable performing QA for LibreOffice, and I am confident that I could perform similar tasks for other sites or services.
The service project was not without its own troubles. One thing that I consistently found difficult was the complexity of many of the bug reports. Many bug reports referenced advanced aspects of LibreOffice or had bugs that were complicated and obtuse. Some days it was easy to find reports that I felt comfortable tackling, while other days it felt like every bug went over my head.
If you are a student or someone that is working on the same or a similar project, I would recommend focusing on the reports that feel doable. If a bug feels too complicated or advanced it is okay to skip it. If a bug feels almost doable, or if you are not able to complete it at that moment, it is okay to save it for later. Futhermore, it is also okay to reach out to your peers or supervisors for help. I had a dedicated supervisor as part of my service learning project, and was able to ask him for advice. If you do not have a dedicated supervisor, sites like LibreOffice often have a support team dedicated to helping people contribute. Find out who is on that team, and do not be afraid to reach out to them.
Comments
Post a Comment