Quick Start :

Download: here! Test what you want Find a bug? Mention it on QA/IRC or file a bug! It's as simple as that -- your help is greatly appreciated!

Intro

Our community is preparing for the release of LibreOffice 5.0.0 (previously denominated 4.5). We've added many new features and fixed loads of bugs (see below...), and we want to make sure that the new version is well tested. You can help to make this release a great one! Be aware however that the translation for this version may not be over and is not yet integrated.

On the 22nd, 23rd and 24th of May we will have an international bug-hunting session, testing the first beta for LibreOffice 5.0.0. Please join us! :-)

How to join

Get the latest version from the pre-releases server.

Linux (64-bit)

Windows

macOS

Note that it will not replace your actual installation, this is a beta version that will install as a developer version

Report bugs you find

When: May 22, 23 and 24

Feel free to join us at any point during these three days.

#Mentors will be available from 08:00 UTC to 22:00 UTC on those dates.

If you can't join us during this session, you're always welcome to help us hunt for bugs on other days. The builds of this particular beta1 (LibreOffice 5.0.0. beta1) will be available until June 7th ;-)

What to test

We aim at:

Doing as much testing on the 5.0.0 as possible

Triaging all already filed issues, so that it's as clear as possible for the developers to step in!

There are always more ways to test: do your regular tasks, structured tests, or playing with the new features..

Choose what suits best for you :-) All testing is great and important, and the more we are, the more chance we have to hunt a bug!

So take one of those:

Your own favorite features

Look at the new 5.0 features

Pick up a test case from the standard regression test using Moztrap

pick a component and check for bugs that were fixed in this release: fixed in 5.0 by component (excluding fixes already backported to 4.4)

Soon we will give some useful queries at this place, what will lead you to bugs that need some checking: xx

Things that underwent major refactorings between 4.4 -> 5.0: <your refactoring here> ... <your refactoring here> ...



Found a bug?

At first, make sure it isn't already reported by searching in our bug database. If it isn't reported yet, you can add it to our bug database using our BSA, which is a simple layout to report bugs. If you are more confident with Bugzilla, you can report your bug using the Bugzilla interface. When you want to discuss first, use chat or mail, fast and direct.

So:

Add it to BugZilla , or

Discuss it on QA/IRC

Via the QA/Mailing List

If there is a bug that you want to pin point as clear as possible, then bibisect (explained by Bjoern Michaelsen) will be a great tool for you (for advanced testers)!

Get a little support

Other users and testers are at IRC and the mailing list to help with any question. Don't be shy, don't hesitate to ask!

More info on Moztrap, to work with our test cases, is here

If you have an idea for a test case, feel welcome to post this at our QA mailing list

Mentors

Who's available to manage the channel? It would be great to have a couple of people providing coverage most of the day...