Jump to content

Quality assurance for KDE apps report, test and confirm bugs

From KDE Community Wiki

Quality assurance for KDE apps: report, test and confirm bugs

As a quality assurance analyst and tester, your role is to ensure KDE software is stable, functional, and usable. Your tasks include:

  • report bugs you encounter while using KDE app(s).
  • test and confirm bugs reported by KDE users on Bugzilla(bug triaging).


Join KDE Quality Testers and Analysts


How to report bugs

Steps:
  1. Create an account on KDE Bugtracker
  2. Report a bug by following the Bugtracker guidelines
  3. Fill out a bug form: guide to filing a bug.
  4. Follow Bug reporting best practices

Back to top

Objectives of the Quality Assurance team

Save developers from the task of auditing, verifying and confirming bugs. Make sure there is enough information behind a bug report to take action.You help developers fix bugs faster.

Back to top

Skills to contribute to the Quality Assurance team

Requirements:
  • basic familiarity with KDE software
  • a rough understanding of how the Linux software stack is arranged
  • no programming knowledge is required

Back to top

Bug triaging: Test and confirm bugs

Tasks:
  1. audit new and old bug reports to make sure they're actionable for developers
  2. verify that a bug exists
  3. confirm if a bug is reproducible
  4. confirm there is enough information for developers to action it.
  5. close bugs that cannot be actioned upon.
    1. And for those that can become actionable, clean them up so that they can be found and actioned by a developer.

Back to top

Benefits of volunteering to the Quality Assurance team

Volunteering in QA has many benefits:
  • Learn programming: Bug triaging is a great way to familiarize yourself with KDE’s software architecture and technical details.
  • Practical support: Your work provides vital support to the KDE community.
  • Skills development: Many team members have learned KDE and Qt programming during the bug triaging process and go on to contribute to the development of KDE software.

Back to top

How to start contributing to the Quality assurance team

Steps:

KDE Bugs

  1. Follow the Bug triaging guidelines.
  2. Open an account at KDE Bugtracker
  3. Read the Bugs documentation.
  4. Audit, verify and confirm bugs. Affirm there is enough information, so developers can take action.


Join KDE Quality Testers and Analysts

Phabricator

In addition to bugs.kde.org, you can contribute through Phabricator:

  1. Most of the quality assurance work is at KDE Bugzilla. However, you should also Watch the Bugsquad project at Phabricator: Bugsquad.
  2. Create an account at identity.kde.org and log in to Phabricator with your account details.
  3. Use the Bugsquad Workboard to complete tasks and tackle issues.


Join KDE Quality Testers and Analysts

Back to top

Summary: Software testers perform the task of reporting, auditing, verifying, confirming and closing bugs. Quality assurance analysts need to be familiar with KDE software and how Linux software is set up.

To start contributing, you need a KDE Bugtracker account. Work happens mostly on KDE Bugtracker. As a KDE software tester, you need to follow the Bugsquad project on KDE Phabricator.

Contact the Quality Assurance team

When you start bug triaging, an existing member can help you out as a mentor. Just stop by the KDE Bugs Matrix group and introduce yourself!

Back to top

Retrieved from "https://community.kde.org/index.php?title=Quality_assurance_for_KDE_apps_report,_test_and_confirm_bugs&oldid=104240"