Editing Extras-testing/QA Checklist/QA Improvements

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 50: Line 50:
== Check List ==
== Check List ==
<pre>
<pre>
-
1. [ ] Licensing ok.
+
1. [ ] Optification ok.
-
2. [ ] Description field ok.
+
2. [ ] Licensing ok.
--
--
3. [ ] Announced features available.
3. [ ] Announced features available.
Line 68: Line 68:
* UI usability issues cannot be used as a reason for vote down.
* UI usability issues cannot be used as a reason for vote down.
* Always test functionality - that is, run the program and try if it works as it should.
* Always test functionality - that is, run the program and try if it works as it should.
 +
* Pls consider adding "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.
imaginary example:
imaginary example:
<pre>
<pre>
1. [x] Licensing ok.
1. [x] Licensing ok.
-
2. [x] Description field ok.
+
2. [x] Optification ok.
-
  FAIL: the package doesn't have a description.
+
  FAIL: the package uses 1512kb from root.
--
--
3. [ ] Announced features available.
3. [ ] Announced features available.

Learn more about Contributing to the wiki.


Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!


Cancel | Editing help (opens in new window)