Talk:Extras-testing/QA checklist
(New page: == What is unacceptable power usage? == *Waking the device from sleep every minute? *Waking the device at all if not in foreground? This is complicated. Maybe someone can define rules thi...) |
(→What is unacceptable power usage?) |
||
| Line 4: | Line 4: | ||
This is complicated. Maybe someone can define rules this way? For starters, I think is good to concentrate on user perceived issues: do you feel the battery lasts less time since you installed that widget? Then hopefully at least the top apps in terms of downloads should be tested using the right tools.--[[User:qgil|qgil]] 11:11, 23 October 2009 (UTC) | This is complicated. Maybe someone can define rules this way? For starters, I think is good to concentrate on user perceived issues: do you feel the battery lasts less time since you installed that widget? Then hopefully at least the top apps in terms of downloads should be tested using the right tools.--[[User:qgil|qgil]] 11:11, 23 October 2009 (UTC) | ||
| + | |||
| + | There are power tools available, just that their documentation isn't there yet. | ||
| + | The internal limits of waking up were pretty tight. But it really is about the type of application, if you want to wardrive for WLANs, then you accept the fact that your battery will be flat really fast. | ||
| + | At least widgets shouldn't do anything if not on screen. | ||
== Security risks? == | == Security risks? == | ||
Revision as of 20:00, 24 October 2009
What is unacceptable power usage?
- Waking the device from sleep every minute?
- Waking the device at all if not in foreground?
This is complicated. Maybe someone can define rules this way? For starters, I think is good to concentrate on user perceived issues: do you feel the battery lasts less time since you installed that widget? Then hopefully at least the top apps in terms of downloads should be tested using the right tools.--qgil 11:11, 23 October 2009 (UTC)
There are power tools available, just that their documentation isn't there yet. The internal limits of waking up were pretty tight. But it really is about the type of application, if you want to wardrive for WLANs, then you accept the fact that your battery will be flat really fast. At least widgets shouldn't do anything if not on screen.
Security risks?
- Connecting to the net without a reason?
- The trick is to know when it's "without a reason" or even if it's the app who is creating the connection or something else. In any case these random or unrequested connections can be cause of a bug and might have an impact in power management and even financial loss, so it's good to ask about them.--qgil 11:11, 23 October 2009 (UTC)
Qt
- How about the criteria for Qt applications? Current Qt -> Maemo look is coming. That can't block the way.
- The toolkit is totally irrelevant in the QA process. As long as the app goes through the usual testing without blockers, it can go to Extras.--qgil 11:11, 23 October 2009 (UTC)