Testing ideas: Difference between revisions

From OLPC
Jump to navigation Jump to search
(Updated the download link for testing build images)
Line 4: Line 4:
**On Fedora: '''yum install qemu'''
**On Fedora: '''yum install qemu'''
*Select a development [[#Development Branches|branch]] to focus your testing on (to be referenced when submitting your bug report)
*Select a development [[#Development Branches|branch]] to focus your testing on (to be referenced when submitting your bug report)
*Download the '''img''' file from [http://download.laptop.org/xo-1/custom/g1g1/en-708-1/ http://download.laptop.org/xo-1/custom/g1g1/en-708-1/]
*Download the '''img''' file from [http://xs-dev.laptop.org/~cscott/xo-1/streams/joyride/ 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'''
*Launch the image with '''qemu -m 256 -soundhw es1370 -net user -net nic,model=rt8130 -hda en708-1.img'''



Revision as of 10:49, 1 July 2008

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

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.