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 7: | Line 7: | ||
== Automatic checks/Autobuilder == | == Automatic checks/Autobuilder == | ||
- | * | + | * Bugtracker field |
- | * | + | * That the description field is not empty |
* Require description field content check only if description has changed | * Require description field content check only if description has changed | ||
* Optified and dependencies are optified too | * Optified and dependencies are optified too | ||
Line 17: | Line 17: | ||
== Package Interface == | == Package Interface == | ||
- | * | + | * Changelog should be displayed. |
* A list of application specific test cases should be displayed (if available. if not available testers should be able to create one.) | * A list of application specific test cases should be displayed (if available. if not available testers should be able to create one.) | ||
* If the package is a library there should be shown packages of application using this library. So everybody can test libraries indirect on application level. | * If the package is a library there should be shown packages of application using this library. So everybody can test libraries indirect on application level. | ||
- | * | + | * Votes should be changeable. |
* Each package that enters or leaves testing triggers a e-mail for the testing squad list | * Each package that enters or leaves testing triggers a e-mail for the testing squad list | ||
* Link to Wiki so that details of test criteria are always accessible to new testers | * Link to Wiki so that details of test criteria are always accessible to new testers | ||
Line 35: | Line 35: | ||
=== Demotion === | === Demotion === | ||
- | * Packages can be demoted at any time by | + | * Packages can be demoted at any time by his maintainers or by a member of the testing squad (demotions should be advertised in the testing squad list). |
- | * When demoting a package there's | + | * When demoting a package there's a option to keep the current app karma (minor issues) or reset it (big blockers), and a text field where should be added the reason for demotion. |
=== Speed Promotion === | === Speed Promotion === | ||
Line 42: | Line 42: | ||
* Changes must be easily visible/documented (run diff agains version in Extras) | * Changes must be easily visible/documented (run diff agains version in Extras) | ||
* Speed promotion is done by selected members of the testing sqad. No extra requirements like "10 days" or minimum package karma. [[User:ossi1967|ossi1967]] | * Speed promotion is done by selected members of the testing sqad. No extra requirements like "10 days" or minimum package karma. [[User:ossi1967|ossi1967]] | ||
- | |||
- | |||
- | |||
- | |||
- | |||
== Check List == | == Check List == | ||
Line 90: | Line 85: | ||
== Testing Squad == | == Testing Squad == | ||
- | * Can demote packages when there | + | * Can demote packages when there is known blockers. |
* Can promote packages when they are stuck in the testing queue for a while without any known blocker. | * Can promote packages when they are stuck in the testing queue for a while without any known blocker. | ||
- | |||
=== Testing Squad mailing list === | === Testing Squad mailing list === | ||
* Public mailing list where are discussed any situation/issue concerning the applications in the maemo.org repositories. | * Public mailing list where are discussed any situation/issue concerning the applications in the maemo.org repositories. | ||
- | * Receives | + | * Receives a automatic notification for each packages that enters testing, is demoted or is promoted. |
[[Category:Quality Assurance]] | [[Category:Quality Assurance]] |
Learn more about Contributing to the wiki.