Community Testing: Difference between revisions
Jump to navigation
Jump to search
m (Reverted edits by GO FUCK YOURSELF (Talk); changed back to last version by Skierpage) |
(mark {{dated}}, make a 2008 and 2009 testing section) |
||
| (19 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{dated}} |
|||
==Purpose== |
|||
{{Community testing}} |
|||
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. |
|||
{{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 where we plan community testing. |
|||
[[Friends in testing]] (in the wiki nav under "Projects > Testing" and in [[Participate]] and such) is where we actually call out to users to help us test. |
|||
== |
== Introduction == |
||
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. |
|||
''Note: This is a strawman draft under discussion on the [http://lists.laptop.org/listinfo/testing testing mailing list].'' |
|||
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. |
|||
* We are a volunteer community group. |
|||
* We test OLPC products and advocate bugfixes on behalf of stakeholders. |
|||
* We are transparent about our processes and our results. |
|||
* We seek to learn and try new things and to teach others what we know. |
|||
* We ask forgiveness, not permission; we value rough consensus, passing tests, and coverage. |
|||
== |
== Mailing list == |
||
# Sign up on the bugtracking system: [http://dev.laptop.org/ Trac] |
|||
# Load the latest developer's build: [[autoreinstallation|Install/upgrade]] |
|||
# Choose a test plan [[User_Stories_Testing|User-Focused Test Plans]] |
|||
# Follow the steps. |
|||
The best place to go to join community testing conversations is the [http://lists.laptop.org/listinfo/testing Testing mailing list], which is also mirrored on an external [http://olpc.396210.n2.nabble.com/Testing-f1469263.html forum]. |
|||
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. |
|||
== 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. |
|||
Now go to the [[Activity Testing Project]] to pick an activity to get started. |
|||
=== 2008 and 2009 testing === |
|||
THANKS for your help! |
|||
Community testing group had weekly [[Community testing meetings]] on IRC, focusing on |
|||
* [[G1G1 Activity testing]] |
|||
* testing the 8.2.1 release, using a lot of test cases summarized in [[Test cases 8.2.1]] coordinated by a [[Test manager]] |
|||
* [[Test_cases_8.2.1#Smoke_tests|smoke tests for 8.2.1]] (and earlier [[Test_cases_8.2.0#Smoke_Test|quick smoke test for release 8.2.0]]) |
|||
* [[Creating new test cases]] and [[Reporting test results]] in a (probably obsolete as of 2010) test case results system. |
|||
== Resources == |
|||
[[Category:Tests]] |
|||
* [[Testing tools]] |
|||
== See also== |
|||
* [[ |
* [[How to test an Activity]] |
||
* [[Friends in testing]] — more for people who want to test out development [[Joyride]] builds. |
|||
Latest revision as of 04:08, 6 July 2011
|
The currency of this article or section may be limited by out-of-date information. There may be relevant discussion on its talk page |
This page is part of the OLPC Community testing Project. How to test an Activity | Reporting test results | Meetings
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 where we plan community testing. Friends in testing (in the wiki nav under "Projects > Testing" and in Participate and such) is where we actually call out to users to help us test.
Introduction
Note: This is a strawman draft under discussion on the testing mailing list.
- We are a volunteer community group.
- We test OLPC products and advocate bugfixes on behalf of stakeholders.
- We are transparent about our processes and our results.
- We seek to learn and try new things and to teach others what we know.
- We ask forgiveness, not permission; we value rough consensus, passing tests, and coverage.
Mailing list
The best place to go to join community testing conversations is the Testing mailing list, which is also mirrored on an external forum.
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.
2008 and 2009 testing
Community testing group had weekly Community testing meetings on IRC, focusing on
- G1G1 Activity testing
- testing the 8.2.1 release, using a lot of test cases summarized in Test cases 8.2.1 coordinated by a Test manager
- smoke tests for 8.2.1 (and earlier quick smoke test for release 8.2.0)
- Creating new test cases and Reporting test results in a (probably obsolete as of 2010) test case results system.