QA/Bugzilla/AutomatedTasks

From The Document Foundation Wiki
< QA‎ | Bugzilla
Jump to: navigation, search

This page is about the Automated tasks of Bugzilla using the script qa-tools.py

Checks

Running the script

  1. Download bugzilla_dump.json from vm174.documentfoundation.org:/home/esc-mentoring/esc/dump/bugzilla_dump.json ( this script can be used: https://redmine.documentfoundation.org/attachments/download/1937/downloadBugzillaDump.sh )
  2. Run 'python3 qa-tools.py' (https://cgit.freedesktop.org/libreoffice/contrib/dev-tools/tree/esc-reporting/qa-tools.py)

The script will warn of the following problems:

movedToFixed

  • Problem: The reporter has moved the bug to RESOLVED FIXED.
  • Solution: The bug should be moved to RESOLVED WORKSFORME unless there's a commit fixing it.

autoConfirmed

  • Problem: The reporter has auto-confirmed his/her own bug.
  • Solution: The bug should be moved back to UNCONFIRMED unless the reporter intends to work on it.

newerVersion

  • Problem: Someone has changed the version field to a newer one.
  • Solution: Version field should be changed back to the previous version unless the previous version was incorrect. Check history to see the previous version.

crashSignature

  • Problem: In order to link Bugzilla with http://crashreport.libreoffice.org, the crashreport field should have the format ["-signature-"], otherwise it doesn't work.
  • Solution: Change the crashreport field to the correct format

addAssigned

  • Problem: Someone has changed the Assignee field and it's different to the default one ( libreoffice-bugs@lists.freedesktop.org ) but the status is not set to ASSIGNED.
  • Solution: Set the status field to ASSIGNED.

removeAssigned

  • Problem: Someone has changed the assignee field to the default one ( libreoffice-bugs@lists.freedesktop.org ) but the status is still ASSIGNED
  • Solution: Change the status back to NEW

addAssignee

  • Problem: Someone has changed the status field to ASSIGNED but the assigne is still the default one ( libreoffice-bugs@lists.freedesktop.org ).
  • Solution: Change the assignee field accordingly

removeAssignee

  • Problem: Someone has changed the status field from ASSIGNED to NEW but the assignee field is still different to the default one ( libreoffice-bugs@lists.freedesktop.org )
  • Solution: Assignee field should be changed to the default one ( libreoffice-bugs@lists.freedesktop.org )

backPortAdded

  • Problem: Someone has added the whiteboard 'backport' but the bug's status is still NEW
  • Solution: Status field should be changed to RESOLVED

fixBugPing

  • Problem: The last comment is from 'libreoffice-commits@lists.freedesktop.org' and it was done more than a month ago.
  • Solution: Leave the following comment:
Polite ping to [developer-name]: is this bug fixed? if so, please close it as RESOLVED FIXED

inactiveAssigned

  • Problem: The bug has been in ASSIGNED status for more than 3 months without any activity.
  • Solution: Change the status to NEW and reset the assignee to default. Leave a comment like:
Dear [developer-name],
This bug has been in ASSIGNED status for more than 3 months without any activity. Resetting it to NEW.
Please assigned it back to yourself if you're still working on this.

emptyAlias

  • Problem: a metabug doesn't have an alias. Having an alias is always good because it makes things more easy visually speaking.
  • Solution: Add an alias describing the metabug

New Contributor

  • Problem: a new contributor has signed up in Bugzilla and he/she has interacted in 3 or more bugs.
  • Solution: Send a welcome email to the new contributor:

Subject:

Welcome to the LibreOffice community!!

Body:

Hello [name],
On behalf of the QA Team, I would like to give you a warm welcome to the LibreOffice project and express my sincere gratitude for the work you have been doing recently.
You can find more information about the QA Team in our wiki page[1] and if you need any help doing QA, don't hesitate to contact the team via IRC [2], Telegram [3] or via the mailing list [4].
Keep up the good work.
Regards
[1]. https://wiki.documentfoundation.org/QA
[2]. https://wiki.documentfoundation.org/QA/IRC
[3]. https://t.me/LibreOffice_QA
[4]. https://wiki.documentfoundation.org/QA/Mailing_List

patchAdded

  • Problem: A patch has been attached to bugzilla along with the keyword 'patch'
  • Solution: Ask the user to submit the patch to gerrit instead. Message:
Dear [user-name],
Thanks for the patch.
Could you please submit it to gerrit as described here:
https://wiki.documentfoundation.org/Development/gerrit/SubmitPatch?

reopened6Months

  • Problem: A bug has been fixed for more than 6 months and it has been reopened
  • Solution: Close the bug as RESOLVED FIXED and ask the user to open a new issue. Message:
Dear [user-name],
This bug has been in RESOLVED FIXED status for more than 6 months.
If the issue is still reproducible with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/, please report a new issue in https://bugs.documentfoundation.org/enter_bug.cgi providing, if     needed, the steps and documents to reproduce it.
Thanks for your understanding and collaboration.
Closing as RESOLVED FIXED

dupeOfDupe

  • Problem: bug A is a duplicate of bug B which is a duplicate of bug C at the same time
  • Solution: Change A to be a duplicate of bug C

Automated tasks

Running the script

  1. Download bugzilla_dump.json from vm174.documentfoundation.org:/home/esc-mentoring/esc/dump/bugzilla_dump.json ( this script can be used: https://redmine.documentfoundation.org/attachments/download/1937/downloadBugzillaDump.sh )
  2. Run 'python3 qa-tools.py automate' (https://cgit.freedesktop.org/libreoffice/contrib/dev-tools/tree/esc-reporting/qa-tools.py)

Obsolete comments

Automatically mark as obsolete the following type of comments when they are not the last comment in the bug:

  1. 'Untouched for a year' comments
  2. Cleaning-out needinfo comments
  3. Cleaning-out needinfo follow-up comments
  4. Comments starting with 'A polite ping, still working on this bug'
  5. Comments containing the text 'I have set the bug's status to 'NEEDINFO

Bug untouched for a year

Ping bug reports with no update in 1 year with the following message:

Stock Message

** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug