View Single Post
Flandry's Avatar
Posts: 1,559 | Thanked: 1,786 times | Joined on Oct 2009 @ Boston
#65
Originally Posted by pycage View Post
IMHO the extras-testing warning should read differently than beware, here be dragons.

Mayb something like
If you use the word "rate", most native english speakers are going to give you their opinion, not the outcome of a series of tests. This is the way i set it up when i have an app in testing and am requesting user testers:
I've promoted it to Extras-testing, which means i consider it ready for end users. Now, it's up to testers to verify that. If you are willing to be a tester, please read about the Extras-Testing repo and make sure the package meets the criteria in the QA Checklist. You can find the testing report page for it here.
The real problem, however, is that there is any need to plug (advertise) testing in the first place. Users eager to download an app can not be expected to do a good job testing it. The ones you can count on to be more impartial are those "weird" (not my word) blessed souls who go through the testing queue because they want to contribute in that way. I wouldn't mention the testing at all in a thread if i thought ten "real" tests was necessary, so i guess my opinion was revealed when i started asking for testers. The way to solve this is either to reduce the total karma so no need is felt to appeal to users to test, or to add a separate requirement for "official testers" so that we can be sure the app is given a thorough test. The first option would be acceptable to me, but the latter (which will require more work on the infrastructure, yes) is the best because it lets the dev sollicit user testing without making them jump through hoops--and this is the process most likely to get him feedback on usabiity issues.

Here's what happens in the rare case that one of the solicited user testers tries to jump through the requested hoops rather than just going and giving a thumbs up:
Ok. I really would like to make report but I´m having little issues. I have read wiki page and it makes little sense to me

So couple of questions before writing report.

...

Maybe I´m not adequate to do testing but i really much would like to learn. It would greatly help if there were more examples in wiki. Right now it feels like its only for professionals :|
And then later:
Originally Posted by slender View Post
Oh. Now i understand. I should give thumbs up only after doing review and copy paste it to comment section.

Douh. I have already voted thumb up after first install because i thought that it´s nice that you put it together. Same thing what i have done on brainstorm or in download section.

Sorry to say but this whole system is really confusing. From wiki it says that system is under construction. Whole comment system should be totally different. It should first ask sections in wiki one by one and after that you could give thumbs up or down.
The current system is too much of one, too little of another.
__________________

Unofficial PR1.3/Meego 1.1 FAQ

***
Classic example of arbitrary Nokia decision making. Couldn't just fallback to the no brainer of tagging with lat/lon if network isn't accessible, could you Nokia?
MAME: an arcade in your pocket
Accelemymote: make your accelerometer more joy-ful

Last edited by Flandry; 2010-01-19 at 13:09.
 

The Following 5 Users Say Thank You to Flandry For This Useful Post: