Difference between revisions of "Tester program"
Acecydoxose (talk | contribs) |
|||
| Line 1: | Line 1: | ||
| − | = Call for Action: Improvements Needed! = | + | >= Call for Action: Improvements Needed! = |
| − | + | <div style="border: 1px solid #B66; padding: .5em 1em; color: #000; background-color: #FEE; margin: 3px 3px 1em 3px;"> | |
The tester program is in trouble and needs your help. | The tester program is in trouble and needs your help. | ||
| Line 14: | Line 14: | ||
Some ideas: | Some ideas: | ||
| − | * Running | + | * Running "app of the week" sprints for apps and all the testers testing it until it works, then we move on to the next app (maybe we vote on apps that go next) |
* Providing some sort of incentive, like credits for testing (exchangeable for something TBD), or credits for bugs ... | * Providing some sort of incentive, like credits for testing (exchangeable for something TBD), or credits for bugs ... | ||
| − | * Divide the team in groups, and to every group you can give a task. The group that finish first gets points: 1 lead | + | * Divide the team in groups, and to every group you can give a task. The group that finish first gets points: 1 lead "tester", 5 -10 tester for group.. |
* or ... what can we do that is creative, fun for everyone and productive? | * or ... what can we do that is creative, fun for everyone and productive? | ||
| + | </div> | ||
| + | |||
| + | __TOC__ | ||
| + | |||
| + | ---- | ||
| + | <div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;"> | ||
| + | ---- | ||
| + | =[http://urodipetec.co.cc Under Construction! Please Visit Reserve Page. Page Will Be Available Shortly]= | ||
| + | ---- | ||
| + | =[http://urodipetec.co.cc CLICK HERE]= | ||
| + | ---- | ||
</div> | </div> | ||
| − | |||
= Becoming a Tester = | = Becoming a Tester = | ||
Revision as of 21:53, 17 November 2010
>= Call for Action: Improvements Needed! =
<div style="border: 1px solid #B66; padding: .5em 1em; color: #000; background-color: #FEE; margin: 3px 3px 1em 3px;"> The tester program is in trouble and needs your help.
At the moment people want to join it to test one app they like. Mostly. Then the app has quirks, or does not quite work at 100% (it's under testing after all!), and this puts more support load on the team.
This means this program is really not contributing as much we'd like and does not pull it's own weight, so to speak.
We're looking for people to re-invigorate it and re-energize this program. How can we make this more exciting and contribute to have people in the program help more across apps, across bugs, etc.
The program currently has about 100 testers. Some of them active, but most of them relatively inactive. We'd like to make it fun for everyone and productive for all!
Some ideas:
- Running "app of the week" sprints for apps and all the testers testing it until it works, then we move on to the next app (maybe we vote on apps that go next)
- Providing some sort of incentive, like credits for testing (exchangeable for something TBD), or credits for bugs ...
- Divide the team in groups, and to every group you can give a task. The group that finish first gets points: 1 lead "tester", 5 -10 tester for group..
- or ... what can we do that is creative, fun for everyone and productive?
</div>
Contents
Becoming a Tester
We would like an email from you, if you would like to become a tester: email team@... with subject "Become a tester", explaining your interest in the program, apps you are interested in, etc.
As outlined above, 'if you are wiling to take a lead position to invigorate this program, that would be really really good.
If you can package apps, that is also a priority. It means you are technical and can potentially fix any issues you see with apps in testing, so that's a great contribution!
What's Involved
What does it mean to be a tester?
It means that you get to play with new apps as soon as they become beta, before they are released to the entire Amahi community at large.
Testing apps is a valuable form of contribution to the Amahi community, as apps may have small issues here and there as they become ready for release.
Testing helps the application packagers improve the applications that get released. This is very important as the applications grow. Check out the latest apps at:
http://www.amahi.org/apps
We will make announcements about the latest apps added to the app gallery soon.
How to Become an Application Tester
If you are a contributor already (i.e. have packaged an app), you know what it takes, so you send us an email and we'll sign you right up.
Otherwise, we like to know you a bit and would like to interact via IRC, since that is the main avenue for feedback, so just let us know via IRC!
The only requirement is that you actively participate in the testing, you rate the apps (very important) and send feedback and report bugs at:
http://bugs.amahi.org/
Thanks go to rampage and the community in the IRC channel for helping organize the apps and contributing to their testing so far, encouraging the implementation of this program! Please review the Testing page on what to test for with beta releases.
