Community Testing: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
(mark {{dated}}, make a 2008 and 2009 testing section) |
||
| (15 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{dated}} |
|||
{{Community testing}} |
{{Community testing}} |
||
{{TOCright}} |
{{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> |
<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 == |
== Introduction == |
||
''Note: This is a strawman draft under discussion on the [http://lists.laptop.org/listinfo/testing testing mailing list].'' |
|||
The community testing team is a volunteer group that seeks: |
|||
to provide developers, users, and stakeholders with an up-to-date, publicly accessible, reliable assessment of how each product and service offered by OLPC meets the needs of those we are trying to serve, |
|||
to be advocates for transparency and community participation within the internal QA group and advocates for testability within the grassroots software, hardware, and content development teams, |
|||
and to constantly seek improvement in our outreach/education efforts, methods, tools, and processes in order to become an increasingly community-run effort. |
|||
* We are a volunteer community group. |
|||
== Meetings and mailing lists == |
|||
* 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 == |
|||
| ⚫ | |||
| ⚫ | |||
| ⚫ | |||
== How you can help == |
== How you can help == |
||
| Line 23: | Line 25: | ||
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. |
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 === |
|||
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. |
|||
| ⚫ | |||
* [[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 == |
== Resources == |
||
* [[Testing tools]] |
* [[Testing tools]] |
||
* [[How to test an Activity]] |
|||
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.