Activity testing project: Difference between revisions

From OLPC
Jump to navigation Jump to search
(New page: == '''WARNING: NOT YET READY FOR PRIME TIME. WORK IN PROGRESS. == == '''Goals for the Activity Testing Project''' == There are a lot of activities out there for the OLPC. Which means th...)
 
m (→‎DEVELOPERS: Submit Your Activity for Testing: avoid redirect (this page is still obsolete))
 
(17 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{merge|Community testing}}
== '''WARNING: NOT YET READY FOR PRIME TIME. WORK IN PROGRESS. ==
{{obsolete|link=[[Community testing]]}}

{{test-nav}}

== '''NOTE: WORK IN PROGRESS. ==

Please drop me a line if you have any feedback, good or bad. --[[User:Gregdek|Gregdek]] 16:38, 9 November 2007 (EST)


== '''Goals for the Activity Testing Project''' ==
== '''Goals for the Activity Testing Project''' ==
Line 15: Line 22:
# Lowest barrier to entry to do meaningful QA work;
# Lowest barrier to entry to do meaningful QA work;
# Presumption that core QA activities are covered by the OLPC team.
# Presumption that core QA activities are covered by the OLPC team.

== '''DEVELOPERS: Submit Your Activity for Testing''' ==

If you are an activity developer, please submit your activity for testing! Follow the instructions in the [[Activity testing guide]].


== '''TESTERS: Get Started Now!''' ==
== '''TESTERS: Get Started Now!''' ==
Line 20: Line 31:
Get started with the OLPC Community QA effort '''right now''':
Get started with the OLPC Community QA effort '''right now''':


# Get OLPC running in emulation.
# '''Get OLPC running in emulation.'''
# Play with Sugar and get familiar with it.
# '''Play with Sugar and get familiar with it.'''
# Claim an activity to test!
# '''Claim an activity to test!'''


=== '''Get OLPC running in emulation''' ===
=== '''Get OLPC running in emulation''' ===
Line 31: Line 42:


The current image approved for QEMU-based testing is the ext3 version of Build 623. [http://olpc.download.redhat.com/olpc/streams/development/build623/devel_ext3/olpc-redhat-stream-development-build-623-20071029_0437-devel_ext3.img.bz2 Download Build 623 now].
The current image approved for QEMU-based testing is the ext3 version of Build 623. [http://olpc.download.redhat.com/olpc/streams/development/build623/devel_ext3/olpc-redhat-stream-development-build-623-20071029_0437-devel_ext3.img.bz2 Download Build 623 now].
: need to confirm whether this is still up to date --[[User:Chihyu|Chihyu]] 15:39, 29 January 2008 (EST)


==== Get OLPC working under QEMU ====
==== Get OLPC working under QEMU ====


We prefer QEMU for emulation, since it's free and available for all platforms, and the OLPC build process generates images that are compatible with QEMU. Follow the [http://wiki.laptop.org/go/Emulating_the_XO/Quick_Start Emulation QuickStart Guide] to get Build 623 working under QEMU.
We prefer QEMU for emulation, since it's free and available for all platforms, and the OLPC build process generates images that are compatible with QEMU. Follow the [[Emulating_the_XO/Quick_Start|Emulation QuickStart Guide]] to get the latest build working under QEMU.


=== '''Become familiar with the workings of Sugar''' ===
=== '''Become familiar with the workings of Sugar''' ===
Line 45: Line 57:


# Open the Browser on your OLPC.
# Open the Browser on your OLPC.
# Click on one of the Activity Download links from the Activity Test Matrix below.
# Click on one of the Activity Download links from the [[Activity Testing Matrix]].
# Go to the Journal.
# Go to the Journal.
# Click on the downloaded activity bundle item.
# Click on the downloaded activity bundle item.
Line 78: Line 90:
Your activity will have a link to a basic test plan. In some cases, this will be a simple, generic test plan; in other cases, it will be a more complex test plan, created by the developer, that is specific to that activity. Step through the test plan and do what it tells you to do.
Your activity will have a link to a basic test plan. In some cases, this will be a simple, generic test plan; in other cases, it will be a more complex test plan, created by the developer, that is specific to that activity. Step through the test plan and do what it tells you to do.


As you proceed through the test plan, edit the wiki plan for the page accordingly. If a test passes, put "pass". If it fails, put "fail", with a link to the bug you file in trac, as detailed on the Activity Testing Matrix page.
As you proceed through the test plan, edit the wiki plan for the page accordingly. If a test passes, put "pass". If it fails, put "fail", with a link to the bug you file in trac, as detailed on the [[Activity Testing Matrix]] page.


If you find issues with the activity that are not included in the test plan, add your issue to the test plan, mark it "failed", and then file a bug in trac.
If you find issues with the activity that are not included in the test plan, add your issue to the test plan, mark it "failed", and then file a bug in trac.
Line 86: Line 98:
If everything checks out, you're done! Edit the Matrix and change the "Status" field from "in progress" to "complete", and give yourself a big slap on the back for a job well done. And then, if you're up to it, claim another activity!
If everything checks out, you're done! Edit the Matrix and change the "Status" field from "in progress" to "complete", and give yourself a big slap on the back for a job well done. And then, if you're up to it, claim another activity!


== '''DEVELOPERS: Build The Matrix!''' ==
== '''Get Help''' ==

The process for putting your activity into the Activity Test Matrix is simple.


For help:
# Edit the Activity Matrix, and add a row with your activity information.
# Drop by irc.freenode.net and join the '''#olpc-qa''' channel and ask a question.
# Create a test plan. Use [[FIXME] this template] as a start.
# Join the [http://mailman.laptop.org/mailman/listinfo/sugar Sugar mailing list] and ask a question.
# Put a watch on your test plan page.


== ''Get Help'' ==


[[category:tests]]
For help, drop by irc.freenode.net and join the #olpc-qa channel.

Latest revision as of 02:36, 27 January 2011

Merge-arrows.gif
It has been suggested that this article or section be merged with Community testing. (Discuss)


542-stopicon.png This page has a more up-to-date location: Community testing


Activity testing project | Testing matrix | Activity testing guide | Activity testing template +/-

To merge: Testing | Testing ideas | Friends in testing


See also: Sugar Labs testing | the Testing mailing list

NOTE: WORK IN PROGRESS.

Please drop me a line if you have any feedback, good or bad. --Gregdek 16:38, 9 November 2007 (EST)

Goals for the Activity Testing Project

There are a lot of activities out there for the OLPC. Which means that there need to be a lot of people testing these activities to make sure that they work as advertised.

Activity testing is also an easy way for newbies to get involved quickly, and to learn about how the OLPC works.

Our goal is to make it as simple as possible for novice users to test new activities, and contribute to the OLPC effort.

(Where "novice user" is probably defined as "someone who knows their way around Linux and open source, but doesn't know much about OLPC.)

Why the focus on activities?

  1. Lowest barrier to entry to do meaningful QA work;
  2. Presumption that core QA activities are covered by the OLPC team.

DEVELOPERS: Submit Your Activity for Testing

If you are an activity developer, please submit your activity for testing! Follow the instructions in the Activity testing guide.

TESTERS: Get Started Now!

Get started with the OLPC Community QA effort right now:

  1. Get OLPC running in emulation.
  2. Play with Sugar and get familiar with it.
  3. Claim an activity to test!

Get OLPC running in emulation

If you have a computer, you can get OLPC running under emulation.

Download the correct OLPC image

The current image approved for QEMU-based testing is the ext3 version of Build 623. Download Build 623 now.

need to confirm whether this is still up to date --Chihyu 15:39, 29 January 2008 (EST)

Get OLPC working under QEMU

We prefer QEMU for emulation, since it's free and available for all platforms, and the OLPC build process generates images that are compatible with QEMU. Follow the Emulation QuickStart Guide to get the latest build working under QEMU.

Become familiar with the workings of Sugar

The user interface, Sugar, will likely be completely new to you. The Sugar instructions should help you figure things out. Read it through. Play with the activities. Find a friend on the mesh and share an activity. Just learn how it works.

Download and play with new activities

There are a handful of activities that ship by default with the OLPC. Here's how to download new activities:

  1. Open the Browser on your OLPC.
  2. Click on one of the Activity Download links from the Activity Testing Matrix.
  3. Go to the Journal.
  4. Click on the downloaded activity bundle item.
  5. Resume the file. The activity should install and load automatically.

Play with whatever activities appeal to you. When you find one that doesn't have a QA Owner, feel free to claim it.  :)

Claim an activity to test

What does it mean to be the test owner for an activity?

It means that you're the person who decides whether an activity is "ready". If you find bugs, you report them, and follow along with them, continuing to test them until they are fixed. It means that you nag the developers, gently but firmly. It means being the person who says "yes, I'm satisfied that this activity is Certified Awesome."

It doesn't have to be a ton of work, and it doesn't have to be hard work -- but it does have to be committed work.

Here's how you do it.

Create a Trac account

Create an account with dev.laptop.org's Trac system. You will use this account when you find bugs. (And you will find bugs. Oh yes, you will.)

Claim an activity

To claim an activity:

  1. Go to the Activity Testing Matrix.
  2. Put your name and email address in the "Test Owner" box for the activity you'd like to claim.
  3. Change the "Status" field from "unclaimed" to "in progress".

Follow the test plan and file bugs

Your activity will have a link to a basic test plan. In some cases, this will be a simple, generic test plan; in other cases, it will be a more complex test plan, created by the developer, that is specific to that activity. Step through the test plan and do what it tells you to do.

As you proceed through the test plan, edit the wiki plan for the page accordingly. If a test passes, put "pass". If it fails, put "fail", with a link to the bug you file in trac, as detailed on the Activity Testing Matrix page.

If you find issues with the activity that are not included in the test plan, add your issue to the test plan, mark it "failed", and then file a bug in trac.

What if everything works?

If everything checks out, you're done! Edit the Matrix and change the "Status" field from "in progress" to "complete", and give yourself a big slap on the back for a job well done. And then, if you're up to it, claim another activity!

Get Help

For help:

  1. Drop by irc.freenode.net and join the #olpc-qa channel and ask a question.
  2. Join the Sugar mailing list and ask a question.