QA Archive

Surpassed the 40,000 closed bugs milestone

As Tommy kindly mentioned on the QA mailing list, this week the LibreOffice project has surpassed the 40,000 resolved bugs milestone – a huge achievement demonstrating the enormous amount of effort the community puts into software quality. If we take a look at the numbers from August 2016 (the month we started

LibreOffice Quality Assurance: six months in statistics (part 2)

This is the second part in our blog series about the LibreOffice QA (quality assurance) community – see here for the first part.

Regressions

During the six month period from 23 November 2016 to 21 May 2017, 553 bugs were identified as regressions by 61 people. This means a feature behaved correctly in the past

Second Bug Hunting Session for LibreOffice 5.4

LibreOffice 5.4 will be announced at the end of July 2017, with a large number of new features which are summarized on the release notes page: https://wiki.documentfoundation.org/ReleaseNotes/5.4. In order to find, report and

LibreOffice Quality Assurance: six months in statistics (part 1)

During the last six months (from 23 November 2016 to 21 May 2017), many things have happened in LibreOffice and in Bugzilla, its bug tracker, where bugs are reported by users, triaged by the quality assurance (QA) team and finally handled by developers, if needed.

New bugs

During this time, 3664 bugs were reported by

First Bug Hunting Session for LibreOffice 5.4

LibreOffice 5.4 is due to be announced at the end of July 2017, with many new features (those already implemented are summarized on the release notes page – https://wiki.documentfoundation.org/ReleaseNotes/5.4 – with much more to come).

In

Video interview: Xisco Fauli, QA engineer for LibreOffice

Xisco Fauli works for The Document Foundation as a quality assurance engineer, helping the QA community handle bug reports, triaging and bibisecting. We talked to him about projects he’s working on, and how everyone can get involved:

Please