svn commit: r1792924 - /openoffice/site/trunk/content/orientation/intro-qa.mdtext

[ms...@apache.org]

Author: mseidel
Date: Thu Apr 27 16:56:08 2017
New Revision: 1792924

URL: http://svn.apache.org/viewvc?rev=1792924&view=rev
Log:
Fixed typos, updated links

Modified:
    openoffice/site/trunk/content/orientation/intro-qa.mdtext

Modified: openoffice/site/trunk/content/orientation/intro-qa.mdtext
URL: http://svn.apache.org/viewvc/openoffice/site/trunk/content/orientation/intro-qa.mdtext?rev=1792924&r1=1792923&r2=1792924&view=diff
==============================================================================
--- openoffice/site/trunk/content/orientation/intro-qa.mdtext (original)
+++ openoffice/site/trunk/content/orientation/intro-qa.mdtext Thu Apr 27 16:56:08 2017
@@ -83,7 +83,7 @@ As mentioned above, QA volunteers need t
 
 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.
 
-Subscribe: [qa-subscribe@openoffice.apache.org](mailto:qa-subscribe@openoffice.apache.org)<br>Post (after subscription): [qa@openoffice.apache.org](mailto:qa@openoffice.apache.org)<br> Unsubscribe: [qa-unsubscribe@openoffice.apache.org](qa-unsubscribe@openoffice.apache.org)
+Subscribe: [qa-subscribe@openoffice.apache.org](mailto:qa-subscribe@openoffice.apache.org)<br>Post (after subscription): [qa@openoffice.apache.org](mailto:qa@openoffice.apache.org)<br> Unsubscribe: [qa-unsubscribe@openoffice.apache.org](mailto:qa-unsubscribe@openoffice.apache.org)
 
 Archives:
 
@@ -108,7 +108,7 @@ Since our job is to find bugs in OpenOff
 
 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.
 
-A more sophisticated approach is to use virtual machines, which can work quite well. [VirtualBox](http://www.virtualbox.org) is a popular virtualization package.
+A more sophisticated approach is to use virtual machines, which can work quite well. [VirtualBox](https://www.virtualbox.org) is a popular virtualization package.
 
 Feel free to ask questions on the QA list about effective ways to manage a test environment.
 
@@ -121,7 +121,7 @@ Once you have your test environment set
 
 Apache Bugzilla is where we track defects:
 
- * [http://issues.apache.org/ooo](http://issues.apache.org/ooo)
+ * [https://bz.apache.org/ooo/](https://bz.apache.org/ooo/)
 
 Bugzilla related documents:
 
@@ -132,7 +132,7 @@ Bugzilla related mailing list:
 
  * [issues@openoffice.apache.org](http://markmail.org/search/+list:org.apache.incubator.ooo-issues). Actvity on issues goes to this mailing list.
 
-Everyone in QA needs a Bugzilla account, which you can get [here](https://issues.apache.org/ooo/createaccount.cgi). 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.
+Everyone in QA needs a Bugzilla account, which you can get [here](https://bz.apache.org/ooo/createaccount.cgi). 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.
 
 ##Easy QA Task: Confirm New Defect Reports
 
@@ -158,7 +158,7 @@ You can now set the Status to CONFIRMED
 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.
 
 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".
+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".
 
 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.
@@ -184,10 +184,10 @@ Manual testing gains you further familia
 
 To get more familiar with AOO, now you can try to perform some manual test cases.
 
-  - Browse test management tool, [Testlink](http://aootesting.adfinis-sygroup.org) to find available test cases.<br>
-  - Read this guide if you are not familiar with Testlink tool. [Testlink usage guide](http://wiki.openoffice.org/wiki/QA/Testlink )
+  - Browse test management tool, [Testlink](http://aootesting.adfinis-sygroup.org) to find available test cases.  
+  - Read this guide if you are not familiar with Testlink tool. [Testlink usage guide](http://wiki.openoffice.org/wiki/QA/Testlink)
 
-##: Easy QA Task: Test Case Authoring
+##Easy QA Task: Test Case Authoring
 
 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.
 
@@ -195,9 +195,9 @@ After some practice on test case executi
 
 Useful guide for writing manual test cases:
 
- * [A guide for writing test case](http://wiki.openoffice.org/wiki/QA/Testcase/How_to_write_test_case)
- * [A simple test case sample](http://wiki.openoffice.org/wiki/QA/Testcase/Sample)
+ * [A guide for writing test case](https://wiki.openoffice.org/wiki/QA/Testcase/How_to_write_test_case)
+ * [A simple test case sample](https://wiki.openoffice.org/wiki/QA/Testcase/Sample)
 
-## Module Completion
+##Module Completion
 
 Once you have done the above, go to our our [Directory of Volunteers](https://cwiki.apache.org/confluence/display/OOOUSERS/Directory+of+Volunteers) wiki page and add or update your information. Also, add an entry for yourself to the [QA Testing Preferences](https://cwiki.apache.org/confluence/display/OOOUSERS/QA+Testing+Preferences) page. Congratulations! Please send a note to [qa@openoffice.apache.org](mailto:qa@openoffice.apache.org?subject=Completed Introduction to QA) so we know.