QA/GetInvolved/ru

From The Document Foundation Wiki
< QA
Jump to: navigation, search
This page is a translated version of the page QA/GetInvolved and the translation is 19% complete.

Outdated translations are marked like this.
Other languages:
čeština • ‎English • ‎italiano • ‎日本語 • ‎русский • ‎中文(简体)‎


Get started

Что такое QA?

QA — сокращение от Quality Assurance(Контроль качества). Он создан для улучшения и проверки новых версий LibreOffice с целью получения конечным пользователями наилучшего программного обеспечения. Контроль качества должен проходить на всех стадиях разработки включая выпуск версии.

Наша основная цель — найти или подтвердить самые смущающие и срочные ошибки и передать их разработчикам, чтобы те могли о них позаботиться. Поэтому, мы как посредники между конечными пользователями и разработчиками, пытаемся приводить отчеты об ошибке в надлежащее качество. Мы пытаемся воспроизвести ошибки, искать дубликаты, дать им правильный приоритет и так далее.

Как принять участие?

Существует много работы как для тех у кого есть специальные навыки, так и для тех у кого этих навыков нет:

Расстановка приоритетов в ошибках

Если вы посмотрите на таблицы, опубликованные в блоге Bjoern[1], то обнаружите, что есть более 5000 открытых ошибки и более 200 из них переданы разработчикам. Мы должны обеспечить для этих ошибок правильные:

  • качество (сортировка на критические и не критические)
  • количество (разработчики должны всегда знать о самых важных ошибках) [2]
  1. Open this query for last month's unconfirmeds (enhancement requests are left out on purpose, some other things filtered out as well)
  2. Pick an interesting bug
  3. Search for duplicates
  4. If the bug is not a duplicate, but has a confusing description or lacks something essential, set the status to NEEDINFO
  5. After trying to reproduce it with both your stable and master build, either set the status to NEW or leave it UNCONFIRMED

Учитывая, что определённая доля подтверждённых ошибок не видела изменения более чем 180 дней, то ясно, что это не поможет тому, чтобы передать больше ошибок разработчикам, в его нынешнем состоянии функционирования. Так что, для команды QA остается только найти наиболее важные ошибки из тех, которые уже представлены: есть сценарий bibisect, который помогает определиться с тем когда в первый раз появилась ошибка.

Проверка и сортировка существующих ошибок

Мы используем эту таблицу, чтобы определить приоритет ошибки. Также добавление корректного status whiteboard будет очень полезно. Подробнее смотри: Сортировка ошибок.

Поиск регрессии

  1. Re-test ~50 bugs untouched for a year or more with a daily build of LibreOffice
  2. Learn about the most important keywords and start using them: accessibility, bibisectRequest, dataLoss, filter:x, needUITest, perf, regression, text:x, wantBacktrace
  3. Install a bunch of old versions and do regression testing for 100 unconfirmed bugs
  4. Learn about priority and severity and request access to the contributors group from a Bugzilla admin
  5. Learn how to get various traces and apply what you learned to reports with wantBacktrace or perf keywords (with no existing traces attached)
  6. Install a different operating system into a virtual machine, so you can do a wider variety of testing and tracing
  7. Start critically evaluating enhancement requests while feeding them to the design team with needsUXEval keyword
  8. Start doing bibisects. Do the tutorial first and move to reports with bibisectRequest keyword.
  9. Learn Python and start creating UI tests
  10. Create Python unit tests
  11. Learn C++ and create cppunit tests

Смотри тест на регрессию. Если вы нашли ошибку регрессии, то вам будет полезен Bibisect чтобы сузить диапазон версий в которых она присутствует.

Проверка нового функционала

Смотри: Проверка нового функционала.

All Linux macOS Windows Android

Улучшение автоматических тестов

last 24 hours last week last month last 6 months

Смотри: автоматические тесты и ручное тестирование.

Сессия "Охота за ошибками"

Check the list here

Try to reproduce the bug

As some bugs are operating system specific, it is always a good idea to test against the same operating system, but if that is not possible, do test it on your current operating system, as most bugs are not operating system specific.

Below you will find boilerplate comments for some common scenarios. For more suggestions on how to comment in reports and browser tools to make commenting efficient, see our Pre-Written Responses.

  • If the bug can be reproduced, set the bug status to NEW and add the following comment:
Thank you for reporting the bug. I can confirm that the bug is present in

[the LibreOffice version details you tested with (can be copied from the HelpAbout LibreOffice dialog)]


  • If the bug can not be reproduced, leave the status as UNCONFIRMED and add the following comment:
Thank you for reporting the bug. I can not reproduce the bug in

[the LibreOffice version details you tested with (can be copied from the HelpAbout LibreOffice dialog)]


  • If the bug report description is too difficult to understand set the bug status to NEEDINFO and add the following comment:
Thank you for reporting the bug. 
Unfortunately without clear steps to reproduce it, we cannot track down the origin of the problem. 
Please provide a clearer set of step-by-step instructions on how to reproduce the problem.
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested information is provided.


  • If a document is needed in order to confirm the bug, set the status to NEEDINFO and add the following comment:
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Note that the attachment will be public, remove any sensitive information before attaching it.
See the QA FAQ Wiki for further detail.)

Additional Steps

  • In case the bug Summary is not clear enough, update it so it better explains the real/main problem being addressed and makes it easier to find duplicates.
  • The Component field can also be updated to better specify which component the problem found in or originates from.
    • Enhancement bug reports requesting the addition of new features need to be first evaluated by the UX team to determine whether it should be implemented or not, so simply set the bug status to NEW, set the Component field to ‘LibreOffice’ and add ‘needsUXEval’ to the Keywords field.
  • Check if the bug is a regression.


Follow the Current development of unconfirmed bugs and see the detailed bug triage instructions for more details.

Test Daily Builds

  1. Download the latest daily build (make sure the Date is recent)
    Linux (RPM & DEB)
    • 64-bit - with GTK3, KDE5 and all helppack languages enabled
    • Updater - Gets updated daily (experimental)
    Windows
    macOS
  2. Install it. (Note that it will not replace your actual installation — this is a development version that will not install as a production version.)
  3. Test it. Check the Release Notes to see what's new in this release.
  4. If you find a bug, please report it here providing all the information available (steps to reproduce the issue, the document affected, detailed description, OS...)

Note: For help, please join #libreoffice-qa connect via webchat IRC.

Test Pre-releases

  1. Download the lastest pre-release version (LibreOffice 6.4 Beta1)
    Linux (64-bit)
    Windows (32-bit)
    Windows (64-bit)
    Mac OS X (64-bits)
  2. Install it. (Note that it will not replace your actual installation.)
  3. Test it. Check the Release Notes to see what's new in this release.
  4. If you find a bug, please report it here providing all the information available (steps to reproduce the issue, the document affected, detailed description, OS...)

Note: For help, please join #libreoffice-qa connect via webchat IRC.

Retest

Every day we ping bugs untouched for more than a year to check whether they may have been fixed in the meantime. More information can be found in the AutomatedTasks article.

Find bugs to retest

  • Bugs pinged today:
All Linux macOS Windows Android
  • Bugs pinged in the last week:
All Linux macOS Windows Android
  • Bugs pinged in the last month:
All Linux macOS Windows Android
  • Bugs pinged in the last three months:
All Linux macOS Windows Android
  • Bugs pinged in the last half a year:
All Linux macOS Windows Android

Try to reproduce the bug

If the bug is present in the latest version of LibreOffice, put the following comment with the LibreOffice version details you tested with (can be copied from the Help ▸ About LibreOffice dialog).

This bug is still present in

[the LibreOffice version details you tested with (can be copied from the Help ▸ About LibreOffice dialog)]

If the bug is not present and you are sure you followed the bug steps correctly, change the status to RESOLVED WORKSFORME and put the following comment:

This bug is no longer reproducible in

[the LibreOffice version details you tested with (can be copied from the Help ▸ About LibreOffice dialog)]

Changing status to RESOLVED WORKSFORME

Please don't ...

  • ... update the version field
  • ... reply via email, instead reply directly on the bug tracker
  • ... set the bug's Status field to RESOLVED - FIXED, since that status is only used when a specific commit has fixed the problem

Additional Steps

Contact

Примечания