Active Topics

 


Reply
Thread Tools
Posts: 434 | Thanked: 325 times | Joined on Sep 2009
#71
Originally Posted by Texrat View Post
There's merit to that, Sasler, but my thinking is we need to first step all the way back to the entry point of the process and start applying rational methodology as opposed to numbers and actions driven by warm fuzzies. "Jailbreaking" quarantine might just ensure more bad apps get out. We need to add more meaning to process steps... especially do what we can to ensure the proposed 5 testers aren't thumbing up or down based on like or dislike.
OK, what about this then:

When a new app reaches a point that it'sfairly functional to get a general idea, a Talk thread is opened for it. Next, say 5 testers are selected. These would then communicate with the developer of any issues and ideas. They would also fill the "Good Quality Check-list". When the developers is happy with the app and all the testers agree that all the points are adequately met, they would then unanimously vote for promotion to Extras. Now guarantee would be needed.

Of course, there should be proper reward to encourage this kind for this kind of commitment. For example, Karma based on the stars and downloads. The developer would get half of it and the testers would all get a fifth of the remaining half. Or something like that.

The important thing would be that this Karma would only be give after the app has been released, so it would encourage active involvement from start to end. Also, the star multiplier, would encourage quality apps.

However, to avoid any hasty releases, just for the sake of some easy Karma. There should be in place some kind of penalty system. That is, is a critical fault is found after the app has been promoted to Extras, it will be demoted again until it will be fixed. And, depending of the gravity of the fault and how obvious it should have been, part of the received Karma would be removed. A part of it would be returned when the problem is fixed again.
 
benny1967's Avatar
Posts: 3,790 | Thanked: 5,718 times | Joined on Mar 2006 @ Vienna, Austria
#72
Originally Posted by VDVsx View Post
Here is a summary of the possible improvements: http://wiki.maemo.org/Extras-testing...A_Improvements

This was not discussed yet with the maemo.org tema, and is far from final, feel free to suggest some improvements.
I did (feel free), but as they were deleted again with no comment or discussion or notification, let my just drop them off here so people can at least read them:
  • Add "Package has description field" as additional item in the check list. Packages without or packages describing themselves as "packagename application" shouldn't go to Extras as this is so easily done.
  • Add a "speed-promote" mechanism a developer can trigger in a few well-defined cases (like: critical bug fixed; changes only to message strings or new language added there etc.). speed promotion could mean: drop requirement for 10 days, drop karma requirement, only some (2-3) of test testing squad will have to give thumbs up. To further ease their work, an automated diff could be created against the sources of the version currently in extras so that testers can be sure what was changed.
 

The Following 5 Users Say Thank You to benny1967 For This Useful Post:
VDVsx's Avatar
Posts: 1,070 | Thanked: 1,604 times | Joined on Sep 2008 @ Helsinki
#73
Originally Posted by benny1967 View Post
I did (feel free), but as they were deleted again with no comment or discussion or notification, let my just drop them off here so people can at least read them:
  • Add "Package has description field" as additional item in the check list. Packages without or packages describing themselves as "packagename application" shouldn't go to Extras as this is so easily done.
  • Add a "speed-promote" mechanism a developer can trigger in a few well-defined cases (like: critical bug fixed; changes only to message strings or new language added there etc.). speed promotion could mean: drop requirement for 10 days, drop karma requirement, only some (2-3) of test testing squad will have to give thumbs up. To further ease their work, an automated diff could be created against the sources of the version currently in extras so that testers can be sure what was changed.
I deleted the first suggestion because I added it to the check list , sorry for the lack of comment and thanks for the suggestion.
__________________
Valério Valério
www.valeriovalerio.org
 

The Following User Says Thank You to VDVsx For This Useful Post:
benny1967's Avatar
Posts: 3,790 | Thanked: 5,718 times | Joined on Mar 2006 @ Vienna, Austria
#74
Originally Posted by VDVsx View Post
I deleted the first suggestion because I added it to the check list , sorry for the lack of comment and thanks for the suggestion.
Ah... my bad... really getting paranoid here lately. Sorry.
 
zerojay's Avatar
Posts: 2,669 | Thanked: 2,555 times | Joined on Apr 2007 @ Halifax, Nova Scotia, Canada
#75
Originally Posted by qgil View Post
Well, I'm sorry for reading this. I will discuss with you apart since it's not related with this thread.

No matter what happened to your wallpapers, if someone is using a copyrighted image without permission then that is a blocker.
My "I'm so done with this" is in reference to reading stuff like that, not giving up on the community or on the tablets/phones, so I don't want you to be concerned about that in any way.

I like seeing all the different suggestions here about what to do for testing. I feel like those Frosted Miniwheats... the professional side of me wants to see a great amount of testing done on every app... and the fun side of me wants it all ASAP!
 

The Following 4 Users Say Thank You to zerojay For This Useful Post:
Texrat's Avatar
Posts: 11,700 | Thanked: 10,045 times | Joined on Jun 2006 @ North Texas, USA
#76
Originally Posted by zerojay View Post
My "I'm so done with this" is in reference to reading stuff like that, not giving up on the community or on the tablets/phones, so I don't want you to be concerned about that in any way.

I like seeing all the different suggestions here about what to do for testing. I feel like those Frosted Miniwheats... the professional side of me wants to see a great amount of testing done on every app... and the fun side of me wants it all ASAP!
Good... then maybe you'll take on the Game Champion role Flandry proposed? pretty please? I'll buy you whatever cereal you like.
__________________
Nokia Developer Champion
Different <> Wrong | Listen - Judgment = Progress | People + Trust = Success
My personal site: http://texrat.net
 
Posts: 53 | Thanked: 49 times | Joined on Jun 2007
#77
Originally Posted by zerojay View Post
My "I'm so done with this" is in reference to reading stuff like that, not giving up on the community or on the tablets/phones, so I don't want you to be concerned about that in any way.

I like seeing all the different suggestions here about what to do for testing. I feel like those Frosted Miniwheats... the professional side of me wants to see a great amount of testing done on every app... and the fun side of me wants it all ASAP!
Then your fun side will download programs from testing queue and maybe from devel and will not wait but then also takes a calculated risk into account. Your rational side keep the serious software which matters (tm) downloaded only from extras.

*I* do not see a problem here.. make backups though.

Last edited by VRe; 2010-01-21 at 09:15.
 
zerojay's Avatar
Posts: 2,669 | Thanked: 2,555 times | Joined on Apr 2007 @ Halifax, Nova Scotia, Canada
#78
Originally Posted by VRe View Post
Then your fun side will download programs from testing queue and maybe from devel and will not wait but then also takes a calculated risk into account. Your rational side keep the serious software which matters (tm) downloaded only from extras.

*I* do not see a problem here.. make backups though.
You really thought I... didn't know this already...?
 
jukey's Avatar
Posts: 246 | Thanked: 204 times | Joined on Jun 2007 @ Potsdam (Germany)
#79
I added the following points to the QA improvement wiki page:
  • A list of application specific test cases should be displayed (if available. if not available testers should be able to create one.)
  • If the package is a library there should be shown packages of application using this library. So everybody can test libraries indirect on application level.

Is this the right place for these suggestions?
__________________
-> Join the SailfishOS Meetup Berlin - every first Monday a month <-

Me on twitter
 

The Following User Says Thank You to jukey For This Useful Post:
VDVsx's Avatar
Posts: 1,070 | Thanked: 1,604 times | Joined on Sep 2008 @ Helsinki
#80
Originally Posted by jukey View Post
I added the following points to the QA improvement wiki page:
  • A list of application specific test cases should be displayed (if available. if not available testers should be able to create one.)
  • If the package is a library there should be shown packages of application using this library. So everybody can test libraries indirect on application level.

Is this the right place for these suggestions?
Yes, thanks for the suggestions.

Can you elaborate a bit more in the first point, don't know if I'm understanding it well. Do you mean something like use cases for the app ? Who should provide this list ?
__________________
Valério Valério
www.valeriovalerio.org
 
Reply

Tags
extras-tesing, finishing the job, quality assurance, quarantine, software quality, user testing


 
Forum Jump


All times are GMT. The time now is 16:29.