What is QA?
QA is short for Quality Assurance. QA identifies problems in our software, confirms problems reported by users, and validates proposed fixes and enhancements so each new version of LibreOffice is more reliable and robust and provides our users with a satisfying tool. We do QA, in different ways, throughout the development of a new release.
Our first goal is to find or confirm the most embarrassing and urgent bugs and hand them over to the developers to take care of them. Therefore we are a bridge between users and developers, and try to guide each bug report to its proper resolution with the goal of improving the user experience. We try to reproduce bugs, give them the right priority, find duplicates, validate proposed fixes, and so on.
1. Create Bugzilla account
In order to test bugs in LibreOffice you need to have an account in Bugzilla. Go here an create a new account. Once you have an account, it is good to go to your preferences and set 'Automatically add me to the CC list of bugs I change' to 'Only if I have no role on them' if you want to be notified whenever someone replies in any of the bug reports you commented in.
2. Install LibreOffice
You should ideally test that the bug is reproducible on a daily Master build or alternatively on the latest release, as the bug may have already been fixed. If you don’t want to affect the LibreOffice version that you currently run on your system, you can install it as a parallel installation. If you are on Linux and want to use the build/release without installing it, you can use this bash script.
Find unconfirmed bugs
- By operating system:
- By Time:
Try to reproduce the bug
As some bugs are operating system specific, it is always a good idea to test against the same operating system, but if that is not possible, do test it on your current operating system, as most bugs are not operating system specific.
- If the bug can be reproduced, set the bug status to NEW and add the following comment:
Thank you for reporting the bug. I can confirm that the bug is present in [the LibreOffice version details you tested with (can be copied from the▸ dialog)]
- If the bug can not be reproduced, leave the status as UNCONFIRMED and add the following comment:
Thank you for reporting the bug. I can not reproduce the bug in [the LibreOffice version details you tested with (can be copied from the▸ dialog)]
- If the bug report description is too difficult to understand set the bug status to NEEDINFO and add the following comment:
Thank you for reporting the bug. Unfortunately without clear steps to reproduce it, we cannot track down the origin of the problem. Please provide a clearer set of step-by-step instructions on how to reproduce the problem. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested information is provided.
- If a document is needed in order to confirm the bug, set the status to NEEDINFO and add the following comment:
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Note that the attachment will be public, remove any sensitive information before attaching it. See the QA FAQ Wiki for further detail.)
- In case the bug Summary is not clear enough, update it so it better explains the real/main problem being addressed and makes it easier to find duplicates.
- The Component field can also be updated to better specify which component the problem found in or originates from.
- Enhancement bug reports requesting the addition of new features need to be first evaluated by the UX team to determine whether it should be implemented or not, so simply set the bug status to NEW, set the Component field to ‘LibreOffice’ and add ‘needsUXEval’ to the Keywords field.
- Check if the bug is a regression.
Test Daily Builds
1. Download the lastest daily build ( make sure the Date is recent )
- Mac OS X
2. Install it. (Note that it will not replace your actual installation — this is a development version that will not install as a production version.)
3. Test it. Check the Release Notes to see what's new in this release.
4. If you find a bug, please report it here providing all the information available ( steps to reproduce the issue, the document affected, detailed description, OS... )
Note: For help, please join connect via webchat IRC ).
Every day we ping bugs untouched for more than a year to check whether they may have been fixed in the meantime. More Info...
Find bugs to retest
- Bugs pinged today:
- Bugs pinged in the last week:
- Bugs pinged in the last month:
- Bugs pinged in the last three months:
- Bugs pinged in the last half a year:
Try to reproduce the bug
If the bug is present in the latest version of LibreOffice, put the following comment with the LibreOffice version details you tested with (can be copied from the▸ dialog).
This bug is still present in [the LibreOffice version details you tested with (can be copied from the Help ▸ About LibreOffice dialog)]
If the bug is not present and you are sure you followed the bug steps correctly, change the status to RESOLVED WORKSFORME and put the following comment:
This bug is no longer reproducible in [the LibreOffice version details you tested with (can be copied from the Help ▸ About LibreOffice dialog)] Changing status to RESOLVED WORKSFORME
Please don't ...
- ... update the version field
- ... reply via email, instead reply directly on the bug tracker
- ... set the bug's Status field to RESOLVED - FIXED, since that status is only used when a specific commit has fixed the problem
- Check if the bug is a regression
Any help is highly appreciated. You can always get in touch