Difference between revisions of "OOo QA Participation Steps"

From Apache OpenOffice Wiki
Jump to: navigation, search
m
 
(13 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
<H1 ALIGN=CENTER><U><B></B></U></H1>
 
<H1 ALIGN=CENTER><U><B></B></U></H1>
−
 
  
 
==Lesson 1: General Overview==
 
==Lesson 1: General Overview==
 
(week 1)  
 
(week 1)  
  
−
# <!--1-->Get a general overview over the OO QA project and how it works [http://qa.openoffice.org/ Quality Assurance] and [http://wiki.services.openoffice.org/wiki/QA_reloaded OOo QA Strategic Concept Papers]  
+
# <!--1-->Get a general overview over the AOO QA project and how it works [https://www.openoffice.org/qa/ Quality Assurance] and [https://www.openoffice.org/qa/QA_reloaded AOO QA Strategic Concept Papers]  
−
# <!--2-->Make familiar with reporting bugs, especially issue handling: [http://qa.openoffice.org/ooQAReloaded/ooQA-ReportBugs.html Quality Assurance Report Bugs]
+
# <!--2-->Make familiar with reporting bugs, especially issue handling: [https://www.openoffice.org/qa/ooQAReloaded/ooQA-ReportBugs.html Quality Assurance Report Bugs]
−
# <!--3-->Register at OOo as ''firstname-HitekSchool''
+
# <!--3-->Register at AOO as ''firstname-HitekSchool''
 
#*An OOo e-mail address [YOUR_NICK]@openoffice.org is automatically generated
 
#*An OOo e-mail address [YOUR_NICK]@openoffice.org is automatically generated
 
#*The [YOUR_NICK]@openoffice.org address is shown as sender if the mail is generated by the issue tracker   
 
#*The [YOUR_NICK]@openoffice.org address is shown as sender if the mail is generated by the issue tracker   
−
# <!--4-->Try mailing list dev@qa.openoffice.org from [http://qa.openoffice.org/servlets/ProjectMailingListList QA Mailing lists]. You can find Introduction to General & Project Mailing Lists [http://www.openoffice.org/mail_list.html here].
+
# <!--4-->Try mailing list qa@openoffice.apache.org from [https://openoffice.apache.org/mailing-lists.html#qa-mailing-list-public QA Mailing lists]. You can find Introduction to General & Project Mailing Lists [https://www.openoffice.org/mail_list.html here].
 
#* Just say hello if you do not have any tasks/questions.
 
#* Just say hello if you do not have any tasks/questions.
−
<!--#* '' How to do it from inside the OOo.???'' -->
+
<!--#* '' How to do it from inside the AOO.???'' -->
−
# <!--5-->Try IRC channel: please find and install an IRC client that suits for you (there are a lot of free tools in the Internet. You can take a look into this [http://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients list of IRC clients] and pick up one which is most convenient for you. Basically, Opera chat tool works pretty well).  
+
# <!--5-->Try IRC channel: please find and install an IRC client that suits for you (there are a lot of free tools on the Internet. You can take a look into this [https://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients list of IRC clients] and pick up one which is most convenient for you. Basically, Opera chat tool works pretty well).  
−
#* The IRC channel on the Freenode server irc://irc.freenode.net/ for this QA project is #qa.openoffice.org
+
#* The IRC channel on the Libera server irc://irc.libera.chat/Openoffice
−
#* OpenOffice.org's localization community hangs out at channel #ooonlc
+
#** You can say "Hi" and "Bye" and disappear very quickly, if you like.
−
#** You can say "Hi" and Bye" and disappear very quickly, if you like.
+
# <!--6-->Create a 'calling card' in oo wiki like: [https://wiki.openoffice.org/wiki/User:Oleg-HitekSchool User:Oleg-HitekSchool] (Find instructions on wiki help).  
−
# <!--6-->Create a 'calling card' in oo wiki like: [http://wiki.services.openoffice.org/wiki/User:Oleg-HitekSchool User:Oleg-HitekSchool] (Find instructions on wiki help).  
+
 
#* Our Wiki pages should be in Hitek School Category
 
#* Our Wiki pages should be in Hitek School Category
−
#* You should include your OOo email address there
+
#* You should include your AOo email address there
 
#*Please, don't create drafts or unneeded pages, wiki documents or contents cannot be permanently deleted, and all changes are saved.
 
#*Please, don't create drafts or unneeded pages, wiki documents or contents cannot be permanently deleted, and all changes are saved.
−
 
  
 
==Lesson 2: Issue Handling==
 
==Lesson 2: Issue Handling==
 
(week 2-3)
 
(week 2-3)
−
<!--please redirect you page that a visitor will automaticly land on 'XXX' page, add your name as author and connect with your calling card -->
+
<!--please redirect your page that a visitor will automatically land on 'XXX' page, add your name as author and connect with your calling card -->
−
# <!--7-->Install office developer version and try different applications: http://download.openoffice.org/680/index.html
+
# <!--7-->Install office developer version and try different applications: https://www.openoffice.org/download/index.html
 
#* Find out what you need for your system and install office developer version on your computer.
 
#* Find out what you need for your system and install office developer version on your computer.
−
#* You can try to work with it and reveal issues. For reporting them you need to use Issue Tracker.
+
#* You can try to work with it and reveal issues. For reporting them, you need to use Bugzilla.
 
# <!--8-->Issue tracker:  
 
# <!--8-->Issue tracker:  
 
#* make familiar with the tooling
 
#* make familiar with the tooling
Line 34: Line 31:
 
#** bug lifecycle,
 
#** bug lifecycle,
 
#** the way to query an issue and to track it
 
#** the way to query an issue and to track it
−
#* take a look at [http://qa.openoffice.org/ooQAReloaded/ooQA-ReportBugs.html Quality Assurance - Report Bugs]
+
#* take a look at [https://www.openoffice.org/qa/ooQAReloaded/ooQA-ReportBugs.html Quality Assurance - Report Bugs]
 
#** make familiar with Issue Handling, Issue Enter
 
#** make familiar with Issue Handling, Issue Enter
 
#* have a look on some issues in real and how they are handled - status changing from unconfirmed to closed
 
#* have a look on some issues in real and how they are handled - status changing from unconfirmed to closed
−
#* write a test issue (and send its number to your group lead)
+
#* write a test issue (and send its number to your group lead).
 +
#* When you find a problem in the application,  you need to find if it is already in the issue database before submit a new one
 
#** check whether similar issue is already described (including duplicate and closed)
 
#** check whether similar issue is already described (including duplicate and closed)
 
#** pay attention to platform, OS and version - you can miss existing issue if you don't choose suitable parameters
 
#** pay attention to platform, OS and version - you can miss existing issue if you don't choose suitable parameters
 
# <!--9-->Confirm 10 issues  
 
# <!--9-->Confirm 10 issues  
−
#* each team site from [http://qa.openoffice.org/ Quality Assurance] has a link called 'open issues'. Have a look inside several issues and try to reproduce them on your system (try different application); write in the issue: "I can reproduce that on system .. with version .. etc. (check how others handles such things) and send the collected issue numbers to your group leader. You need to log in for doing this.
+
#* each team site from [https://www.openoffice.org/qa/ Quality Assurance] has a link called 'open issues'. Have a look inside several issues and try to reproduce them on your system (try different application); write in the issue: "I can reproduce that on system … with version … etc. (check how others handles such things) and send the collected issue numbers to your group leader. You need to log in for doing this.
−
#*If you have comments that didn't confirm an issue but could help to clear them, is welcome. If you cannot confirm, it mostly had reasons: discription is not proper or unprecise , example is not attached etc. and in this case this is also a good comment f.e.: 'I cannot reproduce it like described, please add a step by step description'
+
#*If you have comments that didn't confirm an issue but could help to clear them, is welcome. If you cannot confirm, it mostly had reasons: description is not proper or imprecise, example is not attached etc. and in this case this is also a good comment f.e.: 'I cannot reproduce it like described, please add a step by step description'
−
# <!--10-->Make familiar with the [http://wiki.services.openoffice.org/wiki/EIS EIS] tool.
+
# <s><!--10-->Make familiar with the [http://wiki.services.openoffice.org/wiki/EIS EIS] tool.</s> <font color="red">deprecated</font>
 
#*Look, which CWS is already integrated in which version. If you try to check a fixed issue in a version where the CWS (containing the fix) is not integrated, you get confused why it is not fixed or think it is not properly fixed etc.
 
#*Look, which CWS is already integrated in which version. If you try to check a fixed issue in a version where the CWS (containing the fix) is not integrated, you get confused why it is not fixed or think it is not properly fixed etc.
 
# <!--11-->Close 10 'verified issues'
 
# <!--11-->Close 10 'verified issues'
−
#* site [http://qa.openoffice.org/ooQAReloaded/Docs/QA-Reloaded-Sitemap.html Sitemap of the Quality Assurance Pages] has a link called 'Integrated Issues'. Check if the bug is fixed in a master version (must be already integrated, therefore check in the [http://wiki.services.openoffice.org/wiki/EIS EIS] tool).  
+
#* site [https://www.openoffice.org/qa/ooQAReloaded/Docs/QA-Reloaded-Sitemap.html Sitemap of the Quality Assurance Pages] has a link called 'Integrated Issues'. Check if the bug is fixed in a master version (must be already integrated, therefore check in the <s>[http://wiki.services.openoffice.org/wiki/EIS EIS] tool</s> <font color="red">deprecated</font>).  
 
#*If yes - write in the issue something like: "verified in XY master version - can be closed" (you don't have canconfirm rights to close it by yourselves for now) and send the collected issue numbers to your group leader.
 
#*If yes - write in the issue something like: "verified in XY master version - can be closed" (you don't have canconfirm rights to close it by yourselves for now) and send the collected issue numbers to your group leader.
 
#*send your group lead the collected issue numbers
 
#*send your group lead the collected issue numbers
 
#<!--12-->Join an irc chat 'issue cleaning session' if it is announced  
 
#<!--12-->Join an irc chat 'issue cleaning session' if it is announced  
−
<!--[http://wiki.services.openoffice.org/wiki/issue_hunting_party#Issue_hunting_party_13th_of_January_2009 Issue Hunting Party]-->
+
<!--[https://wiki.openoffice.org/wiki/issue_hunting_party#Issue_hunting_party_13th_of_January_2009 Issue Hunting Party]-->
−
 
+
  
 
==Lesson 3: Manual Testing / TCS==
 
==Lesson 3: Manual Testing / TCS==
 
(week 4)
 
(week 4)
−
# Get a general overview about [http://qa.openoffice.org/ooQAReloaded/ooQA-ManualTesting.html TCS].   
+
# Get a general overview about [https://www.openoffice.org/qa/ooQAReloaded/ooQA-ManualTesting.html TCS].   
 
# Execute 3 [http://qa.openoffice.org/ooQAReloaded/TestcaseSpecifications/OpenOffice.org_3.1 existing TCS-s].  
 
# Execute 3 [http://qa.openoffice.org/ooQAReloaded/TestcaseSpecifications/OpenOffice.org_3.1 existing TCS-s].  
−
# Take a look at [http://specs.openoffice.org/ specification in general].
+
# Take a look at [https://www.openoffice.org/specs specification in general].
 
# Write TCS from the spec (about 30-50 lines/steps) and compare it to the existing one (if any).
 
# Write TCS from the spec (about 30-50 lines/steps) and compare it to the existing one (if any).
 
# Write a TCS that does not exist (with or without SPEC).
 
# Write a TCS that does not exist (with or without SPEC).
−
 
  
 
==Lesson 4: Automated Testing (not obligatory) ==
 
==Lesson 4: Automated Testing (not obligatory) ==
 
(week 5-7)
 
(week 5-7)
−
#Make familiar with the automation area in general: [http://qa.openoffice.org/ooQAReloaded/AutomationTeamsite/ooQA-TeamAutomation.html OO QA-TeamAutomation ]  and [http://qa.openoffice.org/ooQAReloaded/AutomationTeamsite/ooQA-TeamAutomationLinks.html Automation tooling]
+
#Make familiar with the automation area in general: [https://www.openoffice.org/qa/ooQAReloaded/AutomationTeamsite/ooQA-TeamAutomation.html OO QA-TeamAutomation ]  and [https://www.openoffice.org/qa/ooQAReloaded/AutomationTeamsite/ooQA-TeamAutomationLinks.html Automation tooling]
 
#Try the tooling and run an automatic test
 
#Try the tooling and run an automatic test
 
#Take your TCS and make an auto test from it
 
#Take your TCS and make an auto test from it
 
#Overwork your TCS, whether it fits for manual and auto test.
 
#Overwork your TCS, whether it fits for manual and auto test.
−
 
  
 
==Lesson 5: Questions & Answers ==
 
==Lesson 5: Questions & Answers ==
Line 92: Line 87:
  
  
−
''Authors: [http://wiki.services.openoffice.org/wiki/User:Oleg-HitekSchool Oleg Rodov], [http://wiki.services.openoffice.org/wiki/User:NatPol Natalia Polioudova]. 28 December 2008''
+
''Authors: [http://wiki.services.openoffice.org/wiki/User:Oleg-HitekSchool Oleg Rodov], [http://wiki.services.openoffice.org/wiki/User:NatPol Natalia Polioudova] (concepted by [http://wiki.services.openoffice.org/wiki/User:Clu Christoph Lukasiak]). 28 December 2008''
−
 
+
−
''Mentor of the Intership program: [http://wiki.services.openoffice.org/wiki/User:Clu Christoph Lukasiak]''
+
  
 
''Please do not change the logical content of this site without
 
''Please do not change the logical content of this site without

Latest revision as of 07:37, 29 June 2023

Lesson 1: General Overview

(week 1)

  1. Get a general overview over the AOO QA project and how it works Quality Assurance and AOO QA Strategic Concept Papers
  2. Make familiar with reporting bugs, especially issue handling: Quality Assurance Report Bugs
  3. Register at AOO as firstname-HitekSchool
    • An OOo e-mail address [YOUR_NICK]@openoffice.org is automatically generated
    • The [YOUR_NICK]@openoffice.org address is shown as sender if the mail is generated by the issue tracker
  4. Try mailing list qa@openoffice.apache.org from QA Mailing lists. You can find Introduction to General & Project Mailing Lists here.
    • Just say hello if you do not have any tasks/questions.
  5. Try IRC channel: please find and install an IRC client that suits for you (there are a lot of free tools on the Internet. You can take a look into this list of IRC clients and pick up one which is most convenient for you. Basically, Opera chat tool works pretty well).
  6. Create a 'calling card' in oo wiki like: User:Oleg-HitekSchool (Find instructions on wiki help).
    • Our Wiki pages should be in Hitek School Category
    • You should include your AOo email address there
    • Please, don't create drafts or unneeded pages, wiki documents or contents cannot be permanently deleted, and all changes are saved.

Lesson 2: Issue Handling

(week 2-3)

  1. Install office developer version and try different applications: https://www.openoffice.org/download/index.html
    • Find out what you need for your system and install office developer version on your computer.
    • You can try to work with it and reveal issues. For reporting them, you need to use Bugzilla.
  2. Issue tracker:
    • make familiar with the tooling
      • basic rules you should know before sending Issues,
      • bug lifecycle,
      • the way to query an issue and to track it
    • take a look at Quality Assurance - Report Bugs
      • make familiar with Issue Handling, Issue Enter
    • have a look on some issues in real and how they are handled - status changing from unconfirmed to closed
    • write a test issue (and send its number to your group lead).
    • When you find a problem in the application, you need to find if it is already in the issue database before submit a new one
      • check whether similar issue is already described (including duplicate and closed)
      • pay attention to platform, OS and version - you can miss existing issue if you don't choose suitable parameters
  3. Confirm 10 issues
    • each team site from Quality Assurance has a link called 'open issues'. Have a look inside several issues and try to reproduce them on your system (try different application); write in the issue: "I can reproduce that on system … with version … etc. (check how others handles such things) and send the collected issue numbers to your group leader. You need to log in for doing this.
    • If you have comments that didn't confirm an issue but could help to clear them, is welcome. If you cannot confirm, it mostly had reasons: description is not proper or imprecise, example is not attached etc. and in this case this is also a good comment f.e.: 'I cannot reproduce it like described, please add a step by step description'
  4. Make familiar with the EIS tool. deprecated
    • Look, which CWS is already integrated in which version. If you try to check a fixed issue in a version where the CWS (containing the fix) is not integrated, you get confused why it is not fixed or think it is not properly fixed etc.
  5. Close 10 'verified issues'
    • site Sitemap of the Quality Assurance Pages has a link called 'Integrated Issues'. Check if the bug is fixed in a master version (must be already integrated, therefore check in the EIS tool deprecated).
    • If yes - write in the issue something like: "verified in XY master version - can be closed" (you don't have canconfirm rights to close it by yourselves for now) and send the collected issue numbers to your group leader.
    • send your group lead the collected issue numbers
  6. Join an irc chat 'issue cleaning session' if it is announced

Lesson 3: Manual Testing / TCS

(week 4)

  1. Get a general overview about TCS.
  2. Execute 3 existing TCS-s.
  3. Take a look at specification in general.
  4. Write TCS from the spec (about 30-50 lines/steps) and compare it to the existing one (if any).
  5. Write a TCS that does not exist (with or without SPEC).

Lesson 4: Automated Testing (not obligatory)

(week 5-7)

  1. Make familiar with the automation area in general: OO QA-TeamAutomation and Automation tooling
  2. Try the tooling and run an automatic test
  3. Take your TCS and make an auto test from it
  4. Overwork your TCS, whether it fits for manual and auto test.

Lesson 5: Questions & Answers

(week 8)

  1. Reflect what you have learned, ask open questions and finish your documentation


Lesson 6: Individual Project (not obligatory)

(month 1-3)

  1. An individual project (depending on the interests of the single students and the needs of the OOo QA project) in classical QA areas like:
    • Issue Handling
    • TCS
    • Automation
    • Document Writing
    • Individual Tasks




Authors: Oleg Rodov, Natalia Polioudova (concepted by Christoph Lukasiak). 28 December 2008

Please do not change the logical content of this site without acknowledge of the author or the OOo QA Project Lead/Co-Leads.

Retrieved from "https://wiki.openoffice.org/w/index.php?title=OOo_QA_Participation_Steps&oldid=256950"
Personal tools