Community Testing: Difference between revisions
| Line 30: | Line 30: | ||
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]], want to run a [[Test cases 8.2.0|test case on the latest build]] and [[Reporting test results|report results]], 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. |
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]], want to run a [[Test cases 8.2.0|test case on the latest build]] and [[Reporting test results|report results]], 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. |
||
The easiest way to jump in is to help with our current big project, [[G1G1 Activity testing]]. |
|||
The easiest way to jump in is to help with our current big project '''getting all [[Activities/G1G1|G1G1-2008 Activities]] tested by Dec. 25, 2008.''' This will enable us to stress-test a good community testing participation framework so that we can recruit Lots Of New Volunteers starting in January - "please help!" pages are only useful inasmuch as there are people, groups, and tasks standing by to welcome newcomers and help them get started. |
|||
== Resources == |
== Resources == |
||
Revision as of 00:11, 5 December 2008
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.
Meetings and mailing lists
The best place to go to join community testing conversations is the Testing mailing list, which is also mirrored on an external forum.
We meet weekly on IRC. See Community testing meetings for more details.
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, want to run a test case on the latest build and report results, 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.
The easiest way to jump in is to help with our current big project, G1G1 Activity testing.