Extras-testing QA Checklist and Quarantine Period
 

http://wiki.maemo.org/Extras-testing/QA_Checklist

Feedback please. This checklist is common for developers (before promnoting their applications to extras-testing) and betatesters (before giving them farewell to reach Extras).

It would be good to have more specific instructions to measure performace and power management, since sometimes the problems are not obvious specially in only one session or even a couple of days of casual testing.

Re: extras-testing QA Checklist
 

http://wiki.maemo.org/Extras-testing

Are the promotion/demotion criteria shown there up-to-date (10 days, karma >=10) ? At least I can't see voting down an app actually resulting in a karma loss of 4. The pages also seem to be a bit redundant.

Re: extras-testing QA Checklist
 

I just want to add the suggestion to use top in Xterm or maybe loadapplet as an easy way to see if an app has gone off the rails and is eating excessive CPU/battery.

Re: extras-testing QA Checklist
 

Sure the pages are redundant as I had to leave the office right after posting the URL page here. :) I will continue tomorrow.

But please zerojay & co, mae your aditions directly to the wiki page. Thanks!

Re: extras-testing QA Checklist
 

What is the meaning of this item:

Does this mean that programs such as Octave are unacceptable for extras?

Any program that uses enough RAM to swap out system components will cause noticeable harm to respnsiveness, unless you make sure all UI related executables (and their libraries and data pages) are locked in RAM.


There is also:
I think there should be an exception for CLI programs.

Re: extras-testing QA Checklist
 

There must be a way to discern intended from buggy compromises in performance.

One thing is when one app of dedicated use takes a lot of CPU to perform an action understood and desired by the user (render a 3D graph) and another is to have some widget scrolling in such a buggy way that the system becomes sluggish.

And no matter what, Octave just paused in some inactive window should let the system work as usual, 5 minutes same as 5 days after booting the program.

Icon optional for CLI programs sounds reasonable.

Re: extras-testing QA Checklist
 

I think we should provide a standard icon representing the command line that can be used by all CLI applications. Something simple like a zoomed out black screen with a command prompt, for example.

Re: extras-testing QA Checklist
 

I had forgotten the optification. Please check: http://wiki.maemo.org/Extras-testing...root_partition

Can someone explain in that section how to look whether an installed package is optified or not?

Re: extras-testing QA Checklist
 

Tero (I think) started dumping his thoughts at http://wiki.maemo.org/Talk:Extras-testing already - would be good to merge them.

Re: extras-testing QA Checklist
 

Added a section about non-blockers based on comments read from QA testers these days.

http://wiki.maemo.org/Extras-testing...t#Non-blockers