Difference between revisions of "HitekSchool/Group2 Achievements"

From Apache OpenOffice Wiki
Jump to: navigation, search
Line 275: Line 275:
 
|  
 
|  
 
|}
 
|}
 +
May 02 09
 +
 +
{| class="wikitable"
 +
|-
 +
! width="50"|Step
 +
! width="400"|Lesson
 +
! width="75"|Harpreet
 +
|-
 +
|
 +
| Lesson 2: (prolongation)
 +
|
 +
|-
 +
| 3
 +
| Confirm 10 unconfirmed issues
 +
|
 +
|-
 +
|
 +
| Confirmed
 +
| 2
 +
|-
 +
|
 +
| Not reproducible
 +
| 6
 +
|-
 +
| 4
 +
| Make familiar with the EIS tool
 +
| Done|}
 +
 +
 +
 +
{| class="wikitable"
 +
|-
 +
! width="50"|Step
 +
! width="400"|Lesson
 +
! width="75"|Gatis
 +
|-
 +
|
 +
| Lesson 2: (prolongation)
 +
|
 +
|-
 +
| 4
 +
| Make familiar with the EIS tool
 +
| Done
 +
|-
 +
| 5
 +
| Close 10 'verified issues'
 +
| Done
 +
|}
 +
 +
{| class="wikitable"
 +
|-
 +
! width="50"|Step
 +
! width="400"|Lesson
 +
! width="75"|Larysa
 +
! width="75"|Nadejda
 +
! idth="75"|Gatis
 +
|-
 +
|
 +
| Lesson 3: Manual Testing / TCS
 +
|
 +
|
 +
|-
 +
| 1
 +
| Get a general overview about TCS
 +
| Done
 +
| Done
 +
| Done
 +
|-
 +
| 2
 +
| Execute 3 existing TCS
 +
| Done
 +
| Done
 +
| Done
 +
|-
 +
| 3
 +
| Take a look at specification in general
 +
| Done
 +
| Done
 +
| Done
 +
|-
 +
| 4
 +
| Write TCS from the spec and compare it to the existing one
 +
| Done
 +
| Done
 +
| Done
 +
|-
 +
| 4
 +
| Write TCS for a new feature based on the issue #5550
 +
| Done
 +
| Done
 +
| -
 +
|}
 +
 +
  
  

Revision as of 00:11, 11 May 2009

To April 10 2009:

Step Lesson Larysa Gatis Daniel Nadejda Harpreet
Lesson 1: General Overview
1 Get a general overview over the OO QA project and how it works done done done done done
2 Make familiar with reporting bugs done done done done done
3 Register at OOo as firstname-HitekSchool done not this way not this way not this way done
4 Try mailing list dev@qa.openoffice.org done done done done
5 Try IRC channel done done done done done
6 Create a 'calling card' in OO wiki done done done done
Lesson 2: Issue Handling
1 Install office developer version and try different applications done done done done done
2 Issue tracker done done done done done
.
Close Verified Issue hunting party 20 13 reported 18 11 -
.

April 12-18

Step Lesson Larysa Gatis Daniel Nadejda Harpreet
Lesson 1: (prolongation)
6 Create a 'calling card' in OO wiki done done done done done
Lesson 2: Issue Handling ( prolongation )
2 write a test issue done done done done -

April 19-25

Step Lesson Larysa Gatis Daniel Nadejda Harpreet
Lesson 2: (prolongation)
3 Confirm 10 unconfirmed issues
Confirmed 10 3 no report yet 5 -
Not reproducible 5 8 no report yet 11 -

April 26-May 02

Step Lesson Daniel
Lesson 2: (prolongation)
3 Confirm 10 unconfirmed issues
Confirmed 4
Not reproducible 5


Step Lesson Larysa Nadejda
Lesson 2: (prolongation)
4 Make familiar with the EIS tool Done Done
5 Close 10 'verified issues'
Verified - fixed 5 10
Checked - not fixed 3

May 02 09

Step Lesson Harpreet
Lesson 2: (prolongation)
3 Confirm 10 unconfirmed issues
Confirmed 2
Not reproducible 6
4 Make familiar with the EIS tool }


Step Lesson Gatis
Lesson 2: (prolongation)
4 Make familiar with the EIS tool Done
5 Close 10 'verified issues' Done
Step Lesson Larysa Nadejda Gatis
Lesson 3: Manual Testing / TCS
1 Get a general overview about TCS Done Done Done
2 Execute 3 existing TCS Done Done Done
3 Take a look at specification in general Done Done Done
4 Write TCS from the spec and compare it to the existing one Done Done Done
4 Write TCS for a new feature based on the issue #5550 Done Done -




Autor: Natalia Polioudova April 15th, 2009 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