Community Testing: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
mNo edit summary
Line 1: Line 1:
{{Obsolete|link=[[Friends in testing]]}}
{{Community testing}}
{{Draft}}
{{TOCright}}
<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>


'''This page is still under construction.'''


==Purpose==
== Introduction ==
The [[Activities]] on the XO have been developed by community members. Many of them are not well documented and there may not be much information on how to use them; so this testing can be described as 'Descriptive Testing', where you are helping to provide and/or correct the wiki pages that describe how an activity works.


Text goes here, incl. something about how we do our coordinating with the internal OLPC test team.


==Plans==
== Meetings ==
The XO software can be [[Emulation|emulated]] on a number of environments, which means many people are helping out with the testing at the unit and module level for software. Our partners who are closest to the hardware and firmware have provided test resources to test in areas that not accessible in the open source community.


See [[Community testing meetings]].
There are also many people now from early trials or the developers program who have a laptop and can help out with testing on the hardware. We are working on the idea of a 'Test Activity' that loads test cases directly onto the XO; and sends test results back to olpc. More on that as it materializes.


== Recent news ==


* Update snippet from last test meeting
==If you want to help==
* Pointer to meeting notes in general
# Sign up on the bugtracking system: [http://dev.laptop.org/ Trac]
* Activity of the week
# Load the latest developer's build: [[autoreinstallation|Install/upgrade]]
# Choose a test plan [[User_Stories_Testing|User-Focused Test Plans]]
# Follow the steps.


== How you can help ==
If you find a bug you would like to log in trac, please follow these steps. Here is an example bug to look at: [http://dev.laptop.org/ticket/5156]:
# Log into Trac: [http://dev.laptop.org/ Trac]
# Use the search to try and determine if your bug has already been reported
# If a bug like yours is there, you can add notes about your instance of this bug in the add/change section.
# If you need to start a new bug, please try to include the following information:
#* A short, but descriptive title (think about what you just tried to search for)
#* What build you were running; both the OS and the firmware if you can
#* Description of what happened (if the title is not enough)
#* Steps to reproduce the bug -- this is really important and will save a lot of time if it is easy to reproduce
#* Add files or logs to help for debugging. See the [[Test Config Notes]] for info on how to turn on logging
#* Choose the component that you think is involved in this bug.
#* Choose the priority -- how important you think it is.
#* Leave the milestone as 'Never Assigned'. A triage team will review the bugs for priority and add them to the appropriate milestone.


We welcome everyone to the community test group regardless of background, experience, or how much free time you have available; there are tasks for a broad range of skill and commitment levels, and if you don't yet know how to do something for a task you want to take on, we'll work with you to find a way to learn.


Whether you're looking for a [[Test_cases_8.2.0#Smoke_Test|quick smoke test]] you can run and report in less than 45 minutes, have an hour to spend [[Activity testing|testing an Activity]], can spend an afternoon helping us [[creating test cases|create test cases]], want to work on [[testing tools]] or [[automated testing]], or are searching for a potential research or student class project, you'll find it here.
Now go to the [[Activity Testing Project]] to pick an activity to get started.


== Resources ==
THANKS for your help!


* OLPC test scripts
[[Category:Tests]]
* Basic "about testing" portals

* Common QA-relevant Trac queries
== See also==
* Where to ask questions and get help
* [[Testing]]
* [[Friends in testing]] &mdash; more for people who want to test out development [[Joyride]] builds.

Revision as of 20:31, 6 November 2008

  This page is part of the OLPC Community testing Project. How to test an Activity | Reporting test results | Meetings
XO Checkbox


Pencil.png NOTE: The contents of this page are not set in stone, and are subject to change!

This page is a draft in active flux ...
Please leave suggestions on the talk page.

Pencil.png

Translate this page with Google -español -български -中文(中国大陆) -中文(臺灣) -hrvatski -čeština -dansk -Nederlands -suomi -français -Deutsch -Ελληνικά -हिन्दी -italiano -日本語 -한국어 -norsk -polski -português -română -русский -svenska


This page is still under construction.

Introduction

Text goes here, incl. something about how we do our coordinating with the internal OLPC test team.

Meetings

See Community testing meetings.

Recent news

  • Update snippet from last test meeting
  • Pointer to meeting notes in general
  • Activity of the week

How you can help

We welcome everyone to the community test group regardless of background, experience, or how much free time you have available; there are tasks for a broad range of skill and commitment levels, and if you don't yet know how to do something for a task you want to take on, we'll work with you to find a way to learn.

Whether you're looking for a quick smoke test you can run and report in less than 45 minutes, have an hour to spend testing an Activity, can spend an afternoon helping us create test cases, want to work on testing tools or automated testing, or are searching for a potential research or student class project, you'll find it here.

Resources

  • OLPC test scripts
  • Basic "about testing" portals
  • Common QA-relevant Trac queries
  • Where to ask questions and get help