Author: buildbot
Date: Thu Apr 27 16:56:14 2017
New Revision: 1011238
Log:
Staging update by buildbot for openoffice
Modified:
websites/staging/openoffice/trunk/content/ (props changed)
websites/staging/openoffice/trunk/content/orientation/intro-qa.html
Propchange: websites/staging/openoffice/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Apr 27 16:56:14 2017
@@ -1 +1 @@
-1791590
+1792924
Modified: websites/staging/openoffice/trunk/content/orientation/intro-qa.html
==============================================================================
--- websites/staging/openoffice/trunk/content/orientation/intro-qa.html
(original)
+++ websites/staging/openoffice/trunk/content/orientation/intro-qa.html Thu Apr
27 16:56:14 2017
@@ -173,7 +173,7 @@ defects reported by end-users and submit
<h2 id="mailing-list">Mailing List<a class="headerlink" href="#mailing-list"
title="Permanent link">¶</a></h2>
<p>As mentioned above, QA volunteers need to subscribe to our dedicated QA
mail list.</p>
<p>The mailing list is for bug reports, quality assurance for release, beta
tests, manual test, automated tests, etc. This is where the QA community
coordinates its activities.</p>
-<p>Subscribe: <a
href="mailto:qa-subscr...@openoffice.apache.org";>qa-subscr...@openoffice.apache.org</a><br>Post
(after subscription): <a
href="mailto:q...@openoffice.apache.org";>q...@openoffice.apache.org</a><br>
Unsubscribe: <a
href="qa-unsubscr...@openoffice.apache.org">qa-unsubscr...@openoffice.apache.org</a></p>
+<p>Subscribe: <a
href="mailto:qa-subscr...@openoffice.apache.org";>qa-subscr...@openoffice.apache.org</a><br>Post
(after subscription): <a
href="mailto:q...@openoffice.apache.org";>q...@openoffice.apache.org</a><br>
Unsubscribe: <a
href="mailto:qa-unsubscr...@openoffice.apache.org";>qa-unsubscr...@openoffice.apache.org</a></p>
<p>Archives:</p>
<ul>
<li><a
href="http://markmail.org/search/+list:org.apache.incubator.ooo-qa";>Markmail</a></li>
@@ -193,7 +193,7 @@ defects reported by end-users and submit
<h2 id="apache-openoffice-test-builds">Apache OpenOffice Test Builds<a
class="headerlink" href="#apache-openoffice-test-builds" title="Permanent
link">¶</a></h2>
<p>Since our job is to find bugs in OpenOffice, we must run pre-release builds
that contain many bugs. These bugs could be major or minor. They could include
document corruption bugs, crashes, even (in rare cases) bugs that could make
your system unstable. So QA volunteers generally try to separate their QA work
from their normal desktop activities. You don't want to write your thesis on a
test build!</p>
<p>Some volunteers simply use two machines: one dedicated to their testing
work. If things become unstable they can then reinstall the operating system
and start fresh.</p>
-<p>A more sophisticated approach is to use virtual machines, which can work
quite well. <a href="http://www.virtualbox.org";>VirtualBox</a> is a popular
virtualization package.</p>
+<p>A more sophisticated approach is to use virtual machines, which can work
quite well. <a href="https://www.virtualbox.org";>VirtualBox</a> is a popular
virtualization package.</p>
<p>Feel free to ask questions on the QA list about effective ways to manage a
test environment.</p>
<p>Once you have your test environment set up, you need to download and
install the latest OpenOffice build.</p>
<ul>
@@ -203,7 +203,7 @@ defects reported by end-users and submit
<h2 id="bug-handling">Bug Handling<a class="headerlink" href="#bug-handling"
title="Permanent link">¶</a></h2>
<p>Apache Bugzilla is where we track defects:</p>
<ul>
-<li><a
href="http://issues.apache.org/ooo";>http://issues.apache.org/ooo</a></li>
+<li><a href="https://bz.apache.org/ooo/";>https://bz.apache.org/ooo/</a></li>
</ul>
<p>Bugzilla related documents:</p>
<ul>
@@ -214,7 +214,7 @@ defects reported by end-users and submit
<ul>
<li><a
href="http://markmail.org/search/+list:org.apache.incubator.ooo-issues";>iss...@openoffice.apache.org</a>.
Actvity on issues goes to this mailing list.</li>
</ul>
-<p>Everyone in QA needs a Bugzilla account, which you can get <a
href="https://issues.apache.org/ooo/createaccount.cgi";>here</a>. Once you have
a Bugzilla account, you should send a note to the QA list asking to be added to
the "qa-team" group in Bugzilla. This will give you some additional permissions
in Bugzilla. Include your Bugzilla login ID in your request.</p>
+<p>Everyone in QA needs a Bugzilla account, which you can get <a
href="https://bz.apache.org/ooo/createaccount.cgi";>here</a>. Once you have a
Bugzilla account, you should send a note to the QA list asking to be added to
the "qa-team" group in Bugzilla. This will give you some additional permissions
in Bugzilla. Include your Bugzilla login ID in your request.</p>
<h2 id="easy-qa-task-confirm-new-defect-reports">Easy QA Task: Confirm New
Defect Reports<a class="headerlink"
href="#easy-qa-task-confirm-new-defect-reports" title="Permanent
link">¶</a></h2>
<p>Most new volunteers start by reviewing incoming defect reports and
attempting to "confirm" them. The defect reports are often from users and are
often not very clearly written. You learn to "read between the lines" and ask
the user clarifying questions in order to turn the raw report into a
reproducible defect that the developers can debug and fix.</p>
<p>You can get a list of unconfirmed defect reports with from <a
href="https://issues.apache.org/ooo/buglist.cgi?bug_status=UNCONFIRMED&f2=keywords&f3=cf_bug_type&known_name=NeedConfirm&list_id=39759&o2=notsubstring&o3=equals&query_format=advanced&resolution=---&v2=needmoreinfo&v3=DEFECT&order=bug_id%20DESC&query_based_on=NeedConfirm";>this
query</a>.</p>
@@ -236,7 +236,7 @@ You can now set the Status to CONFIRMED
</ol>
<p>Note: Once you have reviewed a bug report, it should only be left in the
UNCONFIRMED state if you are waiting for more information from the user, in
which case you should also set the "needmoreinfo" value into the Keyword field.
In all other cases you should push the report forward to a new status, either
CONFIRMED, RESOLVED/IRREPRODUCIBLE, RESOLVED/INVALID or RESOLVED/DUPLICATE, or
by changing the Issue Type to FEATURE or ENHANCEMENT.</p>
<p>It is a judgement call on whether to immediately mark an issue
RESOLVED/IRREPRODUCIBLE or to send the user a question and wait for a response.
An intermediate approach, when confirming defects report written against older
versions of OpenOffice, is to mark the bug as RESOLVED/IRREPRODUCIBLE and at
the same time add a comment saying, "I was not able to confirm the
-bug given these steps in the current version of OpenOffice (AOO 3.4.1), so I'm
closing this report. If you are still seeing this problem after upgrading to
AOO 3.4.1 please post the details and we can reopen the report".</p>
+bug given these steps in the current version of OpenOffice (AOO 4.1.3), so I'm
closing this report. If you are still seeing this problem after upgrading to
AOO 4.1.3 please post the details and we can reopen the report".</p>
<p>Finally, think of the confirmation process as the opportunity for the QA
Team to improve the value of information we receive from users. We're taking
the raw bug reports, sorting through them, eliminating the ones that do not
report new bugs, and then passing on the good ones to the programmers. So
anything you can do to improve the quality of the incoming defect reports will
help. This includes clarifying the steps needed to reproduce the problem,
attaching sample documents that you might create to reproduce the
problem, improving report titles to make them more accurate/relevant to the
real issue, correcting classifications and adjusting defect priorities.</p>
<h2 id="easy-qa-task-verifying-fixed-defects">Easy QA Task: Verifying Fixed
Defects<a class="headerlink" href="#easy-qa-task-verifying-fixed-defects"
title="Permanent link">¶</a></h2>
@@ -255,16 +255,16 @@ problem, improving report titles to make
<p>Manual testing gains you further familiarity with QA process, by executing
pre-defined test cases and writing up defect reports for any new defects
found.</p>
<p>To get more familiar with AOO, now you can try to perform some manual test
cases.</p>
<ul>
-<li>Browse test management tool, <a
href="http://aootesting.adfinis-sygroup.org";>Testlink</a> to find available
test cases.<br></li>
+<li>Browse test management tool, <a
href="http://aootesting.adfinis-sygroup.org";>Testlink</a> to find available
test cases. </li>
<li>Read this guide if you are not familiar with Testlink tool. <a
href="http://wiki.openoffice.org/wiki/QA/Testlink";>Testlink usage guide</a></li>
</ul>
-<h2 id="easy-qa-task-test-case-authoring">: Easy QA Task: Test Case
Authoring<a class="headerlink" href="#easy-qa-task-test-case-authoring"
title="Permanent link">¶</a></h2>
+<h2 id="easy-qa-task-test-case-authoring">Easy QA Task: Test Case Authoring<a
class="headerlink" href="#easy-qa-task-test-case-authoring" title="Permanent
link">¶</a></h2>
<p>This is a more advanced topic, but after mastery of the above two steps,
and learning to "think like a bug", you will be ready for this.</p>
<p>After some practice on test case execution, now you can start writing new
test cases.</p>
<p>Useful guide for writing manual test cases:</p>
<ul>
-<li><a
href="http://wiki.openoffice.org/wiki/QA/Testcase/How_to_write_test_case";>A
guide for writing test case</a></li>
-<li><a href="http://wiki.openoffice.org/wiki/QA/Testcase/Sample";>A simple test
case sample</a></li>
+<li><a
href="https://wiki.openoffice.org/wiki/QA/Testcase/How_to_write_test_case";>A
guide for writing test case</a></li>
+<li><a href="https://wiki.openoffice.org/wiki/QA/Testcase/Sample";>A simple
test case sample</a></li>
</ul>
<h2 id="module-completion">Module Completion<a class="headerlink"
href="#module-completion" title="Permanent link">¶</a></h2>
<p>Once you have done the above, go to our our <a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/Directory+of+Volunteers";>Directory
of Volunteers</a> wiki page and add or update your information. Also, add an
entry for yourself to the <a
href="https://cwiki.apache.org/confluence/display/OOOUSERS/QA+Testing+Preferences";>QA
Testing Preferences</a> page. Congratulations! Please send a note to <a
href="mailto:q...@openoffice.apache.org?subject=Completed Introduction to
QA">q...@openoffice.apache.org</a> so we know.</p>
