jorge-2 wrote > ... > > 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 automatically.
It is already there. LibreOffice "Regression Testing," both automated and manual, is continual and ongoing: https://wiki.documentfoundation.org/QA/Testing/Regression_Tests 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: https://wiki.documentfoundation.org/MozTrap/User_Guide http://manual-test.libreoffice.org/results/runs/? 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 results bi-weekly. -- View this message in context: http://nabble.documentfoundation.org/Unable-to-Protect-Unprotect-cells-in-Libreoffice-5-tp4158473p4158876.html Sent from the Users mailing list archive at Nabble.com. -- To unsubscribe e-mail to: [email protected] Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ 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
