Re: [Libreoffice-qa] Minutes of ESC call 2014-01-09
Jan Holesovsky-4 wrote * Crashtest update (Markus) + new crash-test / data: + cf. http://dev-builds.libreoffice.org/crashtest/ + http://dev-builds.libreoffice.org/crashtest/2bb1a845a25ca9a39c96f37995453844461aed4e/ + import crashes pretty good now + export still not too good + validation errors still high unfortunately How one can help with these? I have checked some bugs and their status is FIXED or an exported attachment is irrelevant to the bug itself. Should those crashers be marked somehow, bugs reopened or cloned into new reports, BTs added? You can help by fixing the crashes or validation errors. Additionally there are a number of scripting tasks to make the information a bit pretty. IMHO it makes no sense to treat them as normal bugs or check the bug reports. The bug numbers in there are just part of the name of the file. It does not mean that they have any relations to the bug report. From my point of view the crash testing is more a developer tool that we use similar to unit tests to improve quality. From a QA perspective I think you can just enjoy the numbers and the improved quality. Regards, Markus ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] Minutes of ESC call 2014-01-09
Markus Mohrhard schreef op 15/01/14 12:49: You can help by fixing the crashes or validation errors. Additionally there are a number of scripting tasks to make the information a bit pretty. I did make a little python stats script that can display the total number of passers/crashers per mimetype, that is parsed to csv format. Easy to open using LibreOffice (of course ;-) ) and do some calculations/visualization on it. I guess that's already a good starting point for stats, but sadly I don't have time to develop it any further next month or so (exams, master thesis, ...). IMHO it makes no sense to treat them as normal bugs or check the bug reports. The bug numbers in there are just part of the name of the file. It does not mean that they have any relations to the bug report. From my point of view the crash testing is more a developer tool that we use similar to unit tests to improve quality. From a QA perspective I think you can just enjoy the numbers and the improved quality. True. For a non-developer, but QA volunteer, I am only interested in the numbers. (trend per mimetype, and general trend). Kind regards, Joren ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
