Difference between revisions of "HitekSchool"

From Apache OpenOffice Wiki
Jump to: navigation, search
(Participants of the project.)
 
(39 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[http://hitekschool.com/ HitekSchool]] is a Vancouver (Canada) based computer institution which teaches its students all necessary techniques, methodologies and tools they need to know to build a successful career as a Software Tester.
+
[http://hitekschool.com/ HitekSchool] is a Vancouver (Canada) based computer institution which teaches its students all necessary techniques, methodologies and tools they need to know to build a successful career as a Software Tester.
 +
<!--Hitek Computer School is owned and operated by ''Iriol Software Ltd.''-->
 +
Those students  who participate in the OOo QA internship, are corresponding to the free and open mentoring program of OOo: [http://qa.openoffice.org/ooQAReloaded/Docs/QA-Reloaded-HowToStart.html ''QA-Reloaded-HowToStart''] - and publish this way
 +
their experience and outcomes to share them with the OO community.  
  
Hitek Computer School is owned and operated by ''Iriol Software Ltd.''
 
  
 +
== General Agreements: ==
 +
OOo QA train the students coming from the Hitek School in general OOo QA work inside an internship project. The single groups were leaded by Group Leader from Hitek School, supported and mentored by OOo QA Team Leads. Usually the general course take 5-8 weeks, with an individual project taking 1-3 month. The attendees log their work on their 'calling cards' on OOo Wiki, which they can further use for future job applications, references etc. and also get a certificate with a short comment from the supervising Team Lead. The course is honorary, free and open and the resulting work get into the property of OOo and will be published under the corresponding OOo reights.
  
  
==Participants of the project.==
+
== HitekSchool participation in OpenOffice QA: concept ==
  
 +
There will be 2 groups of Hitek School students, each lead by a Group Leader (GL). The GL-s will be responsible for the training of their group members to use OOo tools using the HitekSchool category WIKI pages developed specifically for this ocasion. The WIKI page should be corrected by the GL-s within this process to be more useful and user friendly as per students feedback to them. After all the students get comfortable with the OOo tool kit, every group will get it's own application (or even part of it) for a detailed manual testing. GL’s role on this stage would be to divide the group area of testing to individual projects for every student. After that everyone will perform manual testing of his part in accordance with the OO specifications if such exist for the specific area. All the issues will be reported, handled and analyzed by the students themselves with weekly reporting of the progress to their GLs, who supposed to follow their performance on weekly basis. Such way every student will get his/her hands on experience in the manual testing of Open Office using OOo tooling on one side and the specific area of the OO will be carefully manually tested on another. Interested students will get familiar with the OOo automation tools and get their experience in automated testing of their TCS-s, but it will not be obligatory.
  
There are 2 groups
 
  
Group 1
+
==Participants of the project.==
*[http://wiki.services.openoffice.org/wiki/User:Oleg-HitekSchool Oleg Rodov]
+
  
Group 2:
+
Some general statements for the OOo QA internship  participants:
* [http://wiki.services.openoffice.org/wiki/User:NatPol Natalia Polyudova]
+
  
 +
#Objectives of Internship
  
New HitekSchool project participants can download and install free OpenOffice.org version 3.0 for their system from [http://download.openoffice.org/ Download Page] <br/> and make familiar with an application. They can start their acquaintance with the OOo QA project from the following Initial Steps:
+
#*Contribute to OOo QA process
 +
#*Develop new skills and gain useful work experience
 +
<!--#*Boost marketability -->
 +
#*Combine academic knowledge with hands on skills
 +
#Timeframe
 +
#*2-6 months
 +
<!--#Reference-->
 +
<!--#*Reference provided based on a student performance-->
  
==Initial Steps==
+
 +
Participating groups:
  
'''Step 1:'''
+
[http://wiki.services.openoffice.org/wiki/HitekSchool/Group_1 Group 1] with GL (Group Lead): [http://wiki.services.openoffice.org/wiki/User:Oleg-HitekSchool Oleg Rodov]<br>
 +
[http://wiki.services.openoffice.org/wiki/HitekSchool/Group2 Group 2:] with GL (Group Lead): [http://wiki.services.openoffice.org/wiki/User:NatPol Natalia Polioudova]
  
# <!--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]
 
# <!--2-->Make familiar with reporting bugs, especially issue handling: [http://qa.openoffice.org/ooQAReloaded/ooQA-ReportBugs.html Quality Assurance Report Bugs]
 
  
 +
New project participants can download and install free the current version of OpenOffice.org for their system from [http://download.openoffice.org/ Download Page] and make familiar with its applications.
 +
We suggest to start your acquaintance with the OOo QA project from detailed [http://wiki.services.openoffice.org/wiki/Hitekschool/Initial_Steps Initial Steps].
 +
If you do not came further with anything, you can ask us any time, but always try the 'wiki - OO info sites - mailing list ' first.
 +
If you still have a question, several people probably may have the same problem, too ..
 +
<!--then we have to improve that in any way for the whole project (please see it as a side-project and part of your qa work)-->
 +
So, please, send your hints or comments which can help next newcomers to [http://wiki.services.openoffice.org/wiki/User:NatPol Natalia Polioudova] or [http://wiki.services.openoffice.org/wiki/User:Oleg-HitekSchool Oleg Rodov] to have them
 +
integrated into this [http://wiki.services.openoffice.org/wiki/Hitekschool/Initial_Steps check-list].
  
  
'''Step 2:'''
 
  
# <!--3-->Register at OOo as ''firstname-HitekSchool@openoffice.org''
+
''Autors: [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''
# <!--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].
+
#* Just say hello if you do not have any tasks/questions.
+
<!--#* '' How to do it from inside the OOo.???'' -->
+
# <!--5-->Try IRC channel: please find and install an IRC client that suits you (there are a lot of free tools in the internet).
+
#* The IRC channel on the Freenode server irc://irc.freenode.net/  for this QA project is #qa.openoffice.org
+
#* OpenOffice.org's localization community hangs out at channel #ooonlc
+
#** You can say "Hi" and Bye" and disappear very quickly, if you like.
+
# <!--6-->Try OO wiki (create a simple XXX page and send the link). Find instructions on wiki help.
+
#*Please, don't create drafts or unneeded pages, wiki documents or contents cannot be permanently deleted, and all changes are saved.
+
## Create a 'calling card' in oo wiki like: [http://wiki.services.openoffice.org/wiki/User:Oleg] and connect it with earlier created page
+
##* You should include your OOo email address there
+
  
Please, send your hints or comments which can help next students if you have them
 
 
 
'''Step 3:'''
 
 
 
# <!--7-->Install office developer version and try different applications: http://download.openoffice.org/680/index.html
 
#* Find out what you need for your system and install office developer version at your computer.
 
#* You can try to work with it and reveal issues. For reporting them you need to use Issue Tracker.
 
# <!--8-->Issue tracker:
 
#* make familiar with the tooling
 
#** basic rules you should know before sending Issues,
 
#** bug lifecycle,
 
#** the way to query issue and to track it
 
#* have a look at [http://qa.openoffice.org/ooQAReloaded/ooQA-ReportBugs.html 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)
 
#** check whether similar issue is alreagy described (including duplicate and closed)
 
#** pay attention to platform, OS and version - you can miss existing issue if you don't choose suitable parameters
 
# <!--9-->confirm 10 issues
 
#* each team site from [http://qa.openoffice.org/] has a link called 'open issues'. Have a look inside several issues and try to reproduce them <br/> on your system (try different application); write in the issue: "I can reproduce that on system .. with version .. etc. <br/> (check how others handles such things) and send the collected issue numbers.
 
# <!--10-->Make familiar with the EIS tool (http://wiki.services.openoffice.org/wiki/EIS ).
 
# <!--11-->Close 10 'verified issues'
 
#* each team site from [http://qa.openoffice.org/] 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) , 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) and send the collected issue numbers.
 
 
 
<!--12. join an issue hunting party (http://wiki.services.openoffice.org/wiki/Issue_hunting_party#Issue_hunting_party_13th_of_January_2009 ).-->
 
 
 
 
''Autors: [http://wiki.services.openoffice.org/wiki/User:Oleg-HitekSchool Oleg Rodov], [http://wiki.services.openoffice.org/wiki/User:NatPol Natalia Polyudova] 28 December 2008''<br>
 
''Mentor of the Intership program: [http://wiki.services.openoffice.org/wiki/User:Clu Christoph Lukasiak]''<br>
 
 
''Please do not change the logical content of this site without
 
''Please do not change the logical content of this site without
 
acknowledge of the author or the [http://wiki.services.openoffice.org/wiki/Project_Lead OOo QA Project Lead/Co-Leads].''
 
acknowledge of the author or the [http://wiki.services.openoffice.org/wiki/Project_Lead OOo QA Project Lead/Co-Leads].''
 +
 
[[Category:Quality Assurance]]
 
[[Category:Quality Assurance]]
 +
[[Category:HitekSchool]]

Latest revision as of 13:21, 9 June 2009

HitekSchool is a Vancouver (Canada) based computer institution which teaches its students all necessary techniques, methodologies and tools they need to know to build a successful career as a Software Tester. Those students who participate in the OOo QA internship, are corresponding to the free and open mentoring program of OOo: QA-Reloaded-HowToStart - and publish this way their experience and outcomes to share them with the OO community.


General Agreements:

OOo QA train the students coming from the Hitek School in general OOo QA work inside an internship project. The single groups were leaded by Group Leader from Hitek School, supported and mentored by OOo QA Team Leads. Usually the general course take 5-8 weeks, with an individual project taking 1-3 month. The attendees log their work on their 'calling cards' on OOo Wiki, which they can further use for future job applications, references etc. and also get a certificate with a short comment from the supervising Team Lead. The course is honorary, free and open and the resulting work get into the property of OOo and will be published under the corresponding OOo reights.


HitekSchool participation in OpenOffice QA: concept

There will be 2 groups of Hitek School students, each lead by a Group Leader (GL). The GL-s will be responsible for the training of their group members to use OOo tools using the HitekSchool category WIKI pages developed specifically for this ocasion. The WIKI page should be corrected by the GL-s within this process to be more useful and user friendly as per students feedback to them. After all the students get comfortable with the OOo tool kit, every group will get it's own application (or even part of it) for a detailed manual testing. GL’s role on this stage would be to divide the group area of testing to individual projects for every student. After that everyone will perform manual testing of his part in accordance with the OO specifications if such exist for the specific area. All the issues will be reported, handled and analyzed by the students themselves with weekly reporting of the progress to their GLs, who supposed to follow their performance on weekly basis. Such way every student will get his/her hands on experience in the manual testing of Open Office using OOo tooling on one side and the specific area of the OO will be carefully manually tested on another. Interested students will get familiar with the OOo automation tools and get their experience in automated testing of their TCS-s, but it will not be obligatory.


Participants of the project.

Some general statements for the OOo QA internship participants:

  1. Objectives of Internship
    • Contribute to OOo QA process
    • Develop new skills and gain useful work experience
    • Combine academic knowledge with hands on skills
  1. Timeframe
    • 2-6 months


Participating groups:

Group 1 with GL (Group Lead): Oleg Rodov
Group 2: with GL (Group Lead): Natalia Polioudova


New project participants can download and install free the current version of OpenOffice.org for their system from Download Page and make familiar with its applications. We suggest to start your acquaintance with the OOo QA project from detailed Initial Steps. If you do not came further with anything, you can ask us any time, but always try the 'wiki - OO info sites - mailing list ' first. If you still have a question, several people probably may have the same problem, too .. So, please, send your hints or comments which can help next newcomers to Natalia Polioudova or Oleg Rodov to have them integrated into this check-list.


Autors: 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.

Personal tools