On the page
http://wiki.maemo.org/Extras-testing/QA_Checklist

Loss of utility for testing procedure

Example; "Too much memory used in root partition"
This is an instance of an instructional page becoming vague or changing its focus to design philosophy. The contents of the page should be algorithjic, not narrative. In this section, abandoning additional explanations of "why" and "how" and replacing them explicitly with testing procedure would make it useful for readers to test. There is now no information there besides mentioning dpkg as a tool for listing files - not how it is relevant, or what results should be looked for. Excursions into the links there lead only to more design philosophy, not testing procedure.

A useful entry would have an algorithmic sequence of
tool to use
how to apply it
interpretataion of result
repeat for any additional tools

This type of information would also be appropriate for other sections, such as "Power management issues" and "System performance compromised", even if the only tool is observation. The tool should be specified, the possible results specified, and the results which relate to testing pass/fail specified.