Difference between revisions of "Sugar Kids QA Team"

From Sugar Labs
Jump to navigation Jump to search
(adding in the basics for the Sugar Kids QA Team)
 
m (happpening -> happening)
 
(10 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
All the hardcore programmers are working to make Sugar run on top of Linux, while others are working to make sure that Fedora can natively boot and run the XO laptop.  Lots of QA work happpening in there.  But where are the end-users doing QA for Sugar, in the same way other desktop environments communities do?
+
All the hardcore programmers are working to make Sugar run on top of Linux, while others are working to make sure that Fedora can natively boot and run the XO laptop.  Lots of QA work happening in there.  But where are the end-users doing QA for Sugar, in the same way other desktop environments communities do?
  
 
[[Sugar Kids QA Team]] is the solution.  The Sugar Kids QA Team goals are:
 
[[Sugar Kids QA Team]] is the solution.  The Sugar Kids QA Team goals are:
Line 10: Line 10:
 
== QA Process ==
 
== QA Process ==
  
−
''Nothing here yet ;-) ''
+
We use this template and fill it out during testing:
 +
 
 +
* [[Image:Sugar Kids QA Team-Activity check sheet.odt]] template page
 +
* Download [http://wiki.sugarlabs.org/images/1/1a/Sugar_Kids_QA_Team-Activity_check_sheet.odt ODT file] directly
 +
 
 +
In essence, it contains this form:
 +
 
 +
<hr/>
 +
<hr/>
 +
 
 +
'''Project:''' Quality Assurance for Math4 activities on the XO/Sugar platform
 +
 
 +
'''Team:''' XO Kids QA Team (''Names'')
 +
 
 +
'''Task:''' Basic task description
 +
 
 +
'''Activity resolves:''' 4.N.## Curriculum description.
 +
 
 +
'''Date:''' ''YYYY-MM-DD''
 +
 
 +
'''Method:''' Generic method to start with: Adults loaded new activity and provided N instruction(s), “” The team was directed to collaborate together to figure out how the activity worked and only ask the adults for help if they got stuck.
 +
 
 +
'''Results of method:''' Team ...
 +
 
 +
'''DATA'''
 +
 
 +
'''A. How fun was the activity?'''
 +
# Very un-fun
 +
# Not fun
 +
# A little fun
 +
# Fun
 +
# Very fun!
 +
 
 +
'''Comments:'''
 +
 
 +
'''B. How hard was it to figure out what you were supposed to do?'''
 +
# Very hard
 +
# Hard
 +
# Not hard nor easy
 +
# Easy
 +
# Very easy
 +
 
 +
'''Comments:'''
 +
 
 +
'''C. What didn't work right about the activity?'''
 +
 
 +
'''Comments:'''
 +
 
 +
'''D. TBD'''
 +
 
 +
'''E. TBD'''
 +
 
 +
<hr/>
 +
<hr/>
  
 
== Teams ==
 
== Teams ==
Line 16: Line 69:
 
=== Team Santa Cruz ===
 
=== Team Santa Cruz ===
  
−
''Parent coordinator(s):''  [[User:Quaid|Karsten Wade]]
+
''Parent coordinator(s):''  [[User:Quaid|Karsten Wade]], Larry Cafiero
  
 
''Team:''  Malakai, Saskia, and Mirano are steady members.  We are inviting Sigi, Sophia, and Victoria.
 
''Team:''  Malakai, Saskia, and Mirano are steady members.  We are inviting Sigi, Sophia, and Victoria.
Line 22: Line 75:
 
''Team page:''  
 
''Team page:''  
  
−
[[Category:QA]]
+
[[Category:BugSquad]]
 
[[Category:Sugar Kids QA Team]]
 
[[Category:Sugar Kids QA Team]]
 +
[[Category:Activity Team]]

Latest revision as of 22:40, 4 October 2010

All the hardcore programmers are working to make Sugar run on top of Linux, while others are working to make sure that Fedora can natively boot and run the XO laptop. Lots of QA work happening in there. But where are the end-users doing QA for Sugar, in the same way other desktop environments communities do?

Sugar Kids QA Team is the solution. The Sugar Kids QA Team goals are:

  • Test Sugar activities early and often
  • Provide feedback directly to the Sugar development team, usually through a parent or teacher coordinator
  • Create a repeatable process for kids QA'ing Sugar
  • Document and publicize the process.

QA Process

We use this template and fill it out during testing:

In essence, it contains this form:

Project: Quality Assurance for Math4 activities on the XO/Sugar platform

Team: XO Kids QA Team (Names)

Task: Basic task description

Activity resolves: 4.N.## Curriculum description.

Date: YYYY-MM-DD

Method: Generic method to start with: Adults loaded new activity and provided N instruction(s), “” The team was directed to collaborate together to figure out how the activity worked and only ask the adults for help if they got stuck.

Results of method: Team ...

DATA

A. How fun was the activity?

  1. Very un-fun
  2. Not fun
  3. A little fun
  4. Fun
  5. Very fun!

Comments:

B. How hard was it to figure out what you were supposed to do?

  1. Very hard
  2. Hard
  3. Not hard nor easy
  4. Easy
  5. Very easy

Comments:

C. What didn't work right about the activity?

Comments:

D. TBD

E. TBD

Teams

Team Santa Cruz

Parent coordinator(s): Karsten Wade, Larry Cafiero

Team: Malakai, Saskia, and Mirano are steady members. We are inviting Sigi, Sophia, and Victoria.

Team page:

Retrieved from "https://wiki.sugarlabs.org/index.php?title=Sugar_Kids_QA_Team&oldid=57984"