Testing ideas
Who Should Read This?
This page is for those people who want to volunteer their time to the OLPC project in a software testing capacity. While there are many ways to install a test instance of the Sugar desktop environment on your own computer, this page tries to simplify the task by offering only one. The objective here is to welcome as many potential software testers as possible into the process.
Preparing a Testing Environment
- Install qemu
- On Ubuntu: aptitude install qemu
- On Fedora: yum install qemu
- Select a development branch to focus your testing on (to be referenced when submitting your bug report)
- Download the img file from http://xs-dev.laptop.org/~cscott/xo-1/streams/joyride/
- Launch the image with qemu -m 256 -soundhw es1370 -net user -net nic,model=rt8130 -hda en708-1.img
Question: where do we get the .bz images that can be bzcat'd into 1gb files for ^? Ask CScott
Submitting a Bug Report
Bug reports are submitted on dev.laptop.org. Please consult http://dev.laptop.org/wiki/NewTickets for information pertaining to how to submit a bug report.
Volunteer Team Structure
Once there are a bunch of people helping in the testing effort, how will that volunteer team be organised? For instance, when should the volunteer team's effort be focussed on Joyride, and when should it be focussed on a release candidate? Will there be times when the whole volnteer team should focus on particlar activities? Will the volunteer team be divided into groups specialising in activities.
Stuff like that.
Development Branches
There are four current branches of the software for the XO.
| Update.1 (current) | Stable build that are eligible for signing and distribution |
| Joyride | Testing build where new features are implemented first |
| Faster | |
| OLPC -3 | A rebase of Joyride from Fedora 7 to Fedora 9 |
Signed builds
A Signed build is a build that can be run on any
Deadend instructions
Old Instructions
- See Test issues for QA test cases.
- add a functional test for your activity.
- add a description of who is editing your activity and where its source is to its info-box.