BugHunting Session 4.3.0 RC1

From The Document Foundation Wiki
Jump to: navigation, search
Bughuntban43RC1.png

Quick Start :
* Download: http://www.libreoffice.org/download/pre-releases/
* Test what you want
* Found a bug? Mention at irc / write an issue
Simple as that - all help greatly appreciated !

Intro

Our community is preparing for the release of LibreOffice 4.3.0. 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 not over, but should be almost complete, so don't hesitate to give feedback on it.

On the 20th, 21st and 22nd of June we will have an international bug-hunting session, testing the first RC for LibreOffice 4.3.0. Please join us! :-)

How to join

When: June 20, 21 and 22

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 RC 1 (LibreOffice 4.3.0. RC1) will be available until July 6th ;-)

What to test

We aim at:

  • Doing as much testing on the 4.3.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 4.3 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: issues fixed in 4.3 by component
  • Soon we will give some useful queries at this place, what will lead you to bugs that need some checking: xx

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:

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, 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 man the #libreoffice-qa connect via webchat channel? It would be great to have a couple of people providing coverage most of the day...