How we can help with this ?
We, the users can make one example to each topic of the menu of
LibreOffice can do. Then when coming new version before out we can probe
each example during one week and make a report to programers. With this
reports, just following the menu, they can fix the bugs that apear before
freeing the new version.
The other way is to make a macro to probe each topic of the menu to do
It is already there.
LibreOffice "Regression Testing," both automated and manual, is continual
Individuals, please note that the LibreOffice project runs a MozTrap based
test suite for performing exactly this manual testing--with guided test
cases--but it is woefully underutilized by the broader user community. If
you are interested, check it out:
The learning curve is a little steep for folks to get registered and get a
test case open, but is worth the effort as the results ARE reviewed and
integrated into the QA process. The Engineering Steering Committee reviews
View this message in context:
Sent from the Users mailing list archive at Nabble.com.
To unsubscribe e-mail to: firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy