This is true to a point. The matter of battery consumption is very difficult to define. Can scripts be developed to do the non-trivial/non-obvious things? I mentioned KISStester above, perhaps appending scripts to this? Manually testing of some things may require a better knowledge of the inner workings of the software than the initial developer, which isn't going to grow the pool of testers.

To my mind, there's also difference between a tester and a testing admin. As I've tried to describe above, the testing-admin needs to be able to bring outstanding bugs together and ensure testing/fixing has taken place. Whilst one person can perform testing and admin roles, I'm not convinced the person signing off a peice software needs to be acutely aware of its inner workings so long as it does what it's supposed to and interaction is either intuitive (think grandparents) or described?

I also believe that a testing admin who is not too aware of programming is likely to have a lower threashold of acceptable hence when to promote, resulting in a more working piece of software (obviously the low threashold is a double-edged sword!).

// Edit:

meant say - I'like to volunteer to contribute to this revamped testing effort that aims to get all & sundry from -devel.to full extras. My skills are native english(en-gb) speaker. I can read C/C++ (& edit badly), as well as other languages with C-style structure and syntacx. Been Maemo-ised nearly a year, well and truly! Also, I'd like a way into developing, eventually so by testing is good.