Jump to content

QA/GetInvolved/ko

From The Document Foundation Wiki
< QA
This page is a translated version of the page QA/GetInvolved and the translation is 19% complete.


시작하기

QA는 무엇인가?

QA는 품질 보증(Quality Assurance)의 약자입니다. QA는 소프트웨어의 문제를 식별하고, 사용자가 보고한 문제를 확인하며, 제안된 수정 및 개선 사항의 유효성을 확인하여, 리브레오피스(LibreOffice)의 각각의 새로운 버전을 더욱 더 안정적이며, 견고하고, 사용자들에게 만족스러운 도구로 제공하게 합니다. 새로운 릴리즈의 개발의 전반에 걸쳐서 다양한 방식으로 QA를 진행합니다.

저희의 첫 번째 목표는 가장 심각하고 시급한 버그를 찾아 개발자에게 전달하여 처리하도록 하는 것입니다. 따라서 저희는 사용자와 개발자를 연결하는 다리 역할을 하며, 각 버그 신고가 적절한 해결을 통해 해결될 수 있도록, 사용자 경험 향상을 목표로 하여 최선을 다합니다. 버그를 재현하고, 적절한 우선순위를 부여하고, 중복 버그를 찾고, 제안 된 수정 사항을 검증하는 등의 노력을 기울이고 있습니다.

초보자를 위한 빠른 시작 방법

당신이 처음 이걸 접한다면, 엄청난 양의 기술 문서를 꼼꼼히 살펴보는 데 그다지 흥미가 없을 겁니다. 차라리 바로 시작하고 싶을 겁니다. 자, 시작해 볼까요?

  1. Download and install the latest stable LibreOffice (from the "Fresh" line).
  2. Download and install a recent master build of LibreOffice.
  3. Create an account in The Document Foundation Bugzilla, the bug tracker.
  1. Open this query for last month's unconfirmeds (개선 관련 요청은 의도적으로 제외되었으며, 다른 사항도 필터링되어 있습니다).
  1. Pick an interesting bug.
  2. Search for duplicates.
  3. If the bug is not a duplicate, but has a confusing description or lacks something essential, set the status to NEEDINFO.
  4. After trying to reproduce it with both your stable and master build, either set the status to NEW or leave it UNCONFIRMED.

위의 단계들은 의도적으로 불완전한 분류를 설명합니다. 초보자로 하여금 "완벽한" 분류 결과를 목표로 할 때 고려해야 할 수많은 세부 사항에 압도당하지 않게 하기 위해서입니다. 초보자가 이 간단한 루틴에 익숙해지면 더욱 완벽한 분류로 넘어가야 합니다. 분류 완료를 다른 사람에게 맡기는 것은 효율적이지 않습니다.

QA 분야 에서 개인적인 성장을 위한 로드맵

LibreOffice QA에 진입 하는데 에는, 각자 자신 만의 방법이 있습니다. 하지만 어떤 사람들은 자신이 해야 할 일에 대한 명확한 틀을 통해 더 큰 동기를 부여 받습니다. QA 경력 발전에 대한 제안을 다음과 같이 제시합니다.

  1. 다음 quick start guide 에 설명된 가벼운 분류 방법을 수행하여, 확인되지 않은 버그 약 50개를 찾아냅니다.
  2. 1년 이상 손대지 않은 약 50개의 버그를 다시 테스트합니다. 리베라 오피스의 daily master build을 사용해 보세요.
  3. 가장 중요한 키워드keywords에 대해서 알아보신 후, 아래의 것들도 사용해 보시길 바랍니다. accessibility, bibisectRequest, dataLoss, filter:x, needUITest, perf, regression, text:x, wantBacktrace.
  1. Install a bunch of old versions and do regression testing for 100 unconfirmed bugs.
  2. Learn about priority and severity and request access to the contributors group from a Bugzilla admin.
  3. Learn how to get various traces and apply what you learned to reports with wantBacktrace or perf keywords (with no existing traces attached).
  4. Install a different operating system into a virtual machine, so you can do a wider variety of testing and tracing.
  1. Start critically evaluating enhancement requests while feeding them to the design team with needsUXEval keyword.
  2. Start doing bibisects. Do the tutorial first and move to reports with bibisectRequest keyword.
  3. Learn Python and start creating UI tests.
  4. Create Python unit tests.
  5. Learn C++ and create cppunit tests.

Confirm

Find unconfirmed reports

  • By operating system:
All Linux macOS Windows Android
  • By Time:
last 24 hours last week last month last 6 months

Unconfirmed reports without comments

In order to speed up the triage of unconfirmed reports, we automatically tag them with QA:needsComment in the whiteboard if the report follows these conditions:

  • Inactive for more than 2 weeks
  • No comments from a third person

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 Help ▸ About 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 Help ▸ About 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 <https://wiki.documentfoundation.org/QA/FAQ#sanitize> 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 they should be implemented or not, so simply add ‘needsUXEval’ to the Keywords field and libreoffice-ux-advise@lists.freedesktop.org to the CC.
  • 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)
  2. Install it
  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 IRC:// IRC.

Test Pre-releases

  1. Download the lastest pre-release version
  2. Install it
  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 IRC:// 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 you could:

  1. reproduce the bug in a previous/older version,
  2. but the bug is not present anymore in the latest version,

change the status to RESOLVED WORKSFORME and put the following comment:

Thank you for reporting the bug. I can confirm that the bug is present in

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

This bug is no longer reproducible in

[the LibreOffice "latest" 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

Any help is highly appreciated. You can always get in touch