There are lots of different areas and tasks for all skill levels.
The most common thing we do is confirm bug reports.
The process of confirming a bug can be as simple as replying to the report that you could or couldn't reproduce the issue with such and such a version and operating system.
There is, of course, an ideal procedure that involves improving the report in every way: https://wiki.documentfoundation.org/QA/BugTriage
Perhaps the easiest task is retesting old reports that have already been confirmed and analyzed. Recently I closed 50 reports in a single week by retesting alone!
Any particular area, which you would like to hear details on?
After creating an account on the TDF Bugzilla, you can do a couple of tweaks:
Preferences - Account Information - Your real name: you should input a nickname or a real name here.
This is good so that you can keep up with the bugs you comment on or change status:
General Preferences - Automatically add me to the CC list of bugs I change - Only if I have no role on them
If you want to start with arguably the easiest task, testing, if old bug reports are still valid, you can look at this list:
That query is a mass ping made by QA admin during April 18-19. There are almost 300 reports that didn't get a reply from their original reporter. Many of those can be closed as RESOLVED WORKSFORME, like is described in the QA admin ping message.
If the bug is still valid in the latest version, comment "Reproduced" (when going through steps) or "Confirmed" (when the problem is apparent at a glance) and add your LibreOffice version information and the operating system you use (Windows 7, Ubuntu 15.04, Fedora 22, OS X 10.10..). It is handy to have the repetitive version info somewhere always open, so you can copy + paste. Some use browser addons to quickly paste text.
If you are convinced that the bug has disappeared (especially when your operating system matches the ones tested previously - sometimes bugs depend on the OS), you can add a short comment with your version info etc. and at the same time change the status to RESOLVED WORKSFORME.
Sometimes the bug has changed a bit for the better, but not completely disappeared and you should explain it in your comment.
Sometimes the information of your Linux desktop environment or window manager is relevant.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
Hope your are doing good
My self raja, having 5+ yrs excellent testing experience in various domains
i am interest to work with you
So kindly give me the project to work right away
Raja T
+919052762101
thumatiraja@gmail.com
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I am software tester by profession. I am interested in taking up this assignment. sakthi_test@hotmail.com is my mail id. Please contact me if still u need help.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
LibreOffice quality assurance team is constantly looking for new members: https://wiki.documentfoundation.org/QA
There are lots of different areas and tasks for all skill levels.
The most common thing we do is confirm bug reports.
The process of confirming a bug can be as simple as replying to the report that you could or couldn't reproduce the issue with such and such a version and operating system.
There is, of course, an ideal procedure that involves improving the report in every way: https://wiki.documentfoundation.org/QA/BugTriage
Perhaps the easiest task is retesting old reports that have already been confirmed and analyzed. Recently I closed 50 reports in a single week by retesting alone!
Testing in anticipation of a release is explained here:
https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
Bibisecting of known regressions is a powerful tool that can boost bug fixing tremendously: https://wiki.documentfoundation.org/QA/HowToBibisect
Miscellaneous cleanup tasks are listed here: https://wiki.documentfoundation.org/QA/Bugzilla/Gardening
For communication we have IRC and a mailing list:
https://webchat.freenode.net/?channels=#libreoffice-qa
http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
As mentioned in the subject, I can personally mentor you and the IRC channel usually has people, who can answer questions.
On IRC my nick is beluga_
Last edit: Buovjaga 2015-05-17
Interested, Please update the details.
Any particular area, which you would like to hear details on?
After creating an account on the TDF Bugzilla, you can do a couple of tweaks:
Preferences - Account Information - Your real name: you should input a nickname or a real name here.
This is good so that you can keep up with the bugs you comment on or change status:
General Preferences - Automatically add me to the CC list of bugs I change - Only if I have no role on them
If you want to start with arguably the easiest task, testing, if old bug reports are still valid, you can look at this list:
https://bugs.documentfoundation.org/buglist.cgi?bug_status=NEW&chfieldfrom=2015-04-18&chfieldto=2015-04-20&list_id=538624&longdesc=This%20NEW%20Message%20was%20generated%20on%3A%202015-04-18&longdesc_type=allwordssubstr&product=LibreOffice&query_format=advanced&resolution=---
That query is a mass ping made by QA admin during April 18-19. There are almost 300 reports that didn't get a reply from their original reporter. Many of those can be closed as RESOLVED WORKSFORME, like is described in the QA admin ping message.
If the bug is still valid in the latest version, comment "Reproduced" (when going through steps) or "Confirmed" (when the problem is apparent at a glance) and add your LibreOffice version information and the operating system you use (Windows 7, Ubuntu 15.04, Fedora 22, OS X 10.10..). It is handy to have the repetitive version info somewhere always open, so you can copy + paste. Some use browser addons to quickly paste text.
If you are convinced that the bug has disappeared (especially when your operating system matches the ones tested previously - sometimes bugs depend on the OS), you can add a short comment with your version info etc. and at the same time change the status to RESOLVED WORKSFORME.
Sometimes the bug has changed a bit for the better, but not completely disappeared and you should explain it in your comment.
Sometimes the information of your Linux desktop environment or window manager is relevant.
Hi,
Hope your are doing good
My self raja, having 5+ yrs excellent testing experience in various domains
i am interest to work with you
So kindly give me the project to work right away
Raja T
+919052762101
thumatiraja@gmail.com
Hi,
I am software tester by profession. I am interested in taking up this assignment. sakthi_test@hotmail.com is my mail id. Please contact me if still u need help.
It sounds interesting.
Still looking for QA assistance? If so, I believe I would be interested.
I will make this clear: we will never stop looking for QA assistance :)
Hi, I am interested in taking up this assignment.
Thank you.
Last edit: Tan Siew Ling 2016-05-03
Sounds interesting would like to join