Difference between revisions of "Sugar Kids QA Team"
(rename category Activity to Activity_Team) |
(addiing in the QA form we worked out -- both the OpenOffice.org template link, and the actual bits right here for reference.) |
||
Line 10: | Line 10: | ||
== QA Process == | == QA Process == | ||
− | '' | + | We can use the template ([[:Image:Sugar Kids QA Team Report Template|ODT]] format) to fill 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?''' | ||
+ | # 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''' | ||
== Teams == | == Teams == |
Revision as of 13:20, 4 May 2009
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?
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 can use the template (ODT format) to fill 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?
- 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
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: