Extras-testing/QA Checklist/QA Improvements - Revision history

jaffa: /* Speed Promotion */ Alternative

2010-05-12T13:12:07Z

Speed Promotion: Alternative

← Older revision		Revision as of 13:12, 12 May 2010
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]]
		+
		+	=== Speed Promotion (alternative) ===
		+	Alternate suggestion: given that the smallest change by a developer can cause a serious regression, and there's no way round that - is that once a package reaches the "tipping point" (say, 5 days and 8 votes) another version of the package is let into Extras-testing.
		+
		+	However, people can still rate the earlier version (although not install it) and get it through; whilst the newer version starts its QA process. Obviously if there's a bug, the developer can demote their earlier version and prevent it going through to Extras. --[[User:jaffa\|Jaffa]] 13:12, 12 May 2010 (UTC)

	== Check List ==		== Check List ==

tor: Minor grammar fixes

2010-03-09T11:47:43Z

Minor grammar fixes

← Older revision		Revision as of 11:47, 9 March 2010
Line 85:		Line 85:

	== Testing Squad ==		== Testing Squad ==
-	* Can demote packages when there is known blockers.	+	* Can demote packages when there are 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.
	* Can promote packages in speed promotion process [[User:ossi1967\|ossi1967]]		* Can promote packages in speed promotion process [[User:ossi1967\|ossi1967]]
Line 91:		Line 91:
	=== 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 a automatic notification for each ~~packages~~ that enters testing, is demoted or is promoted.	+	* Receives an automatic notification for each package that enters testing, is demoted or is promoted.
	[[Category:Quality Assurance]]		[[Category:Quality Assurance]]

tor: Minor grammar fixes

2010-03-09T11:45:26Z

Minor grammar fixes

← Older revision		Revision as of 11:45, 9 March 2010
Line 35:		Line 35:

	=== Demotion ===		=== Demotion ===
-	* Packages can be demoted at any time by ~~his~~ maintainers ('''Implemented''') or by a member of the testing squad (demotions should be advertised in the testing squad list).	+	* Packages can be demoted at any time by their maintainers ('''Implemented''') or by a member of the testing squad (demotions should be advertised in the testing squad list).
-	* 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.	+	* When demoting a package there's an 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 ===

vdvsx: /* Package Interface */

2010-03-07T14:28:41Z

Package Interface

← Older revision		Revision as of 14:28, 7 March 2010
Line 17:		Line 17:

	== Package Interface ==		== Package Interface ==
-	* Changelog should be displayed - '''~~Under development (10.02-03)~~'''	+	* <s>Changelog should be displayed</s> - '''Done'''
	* 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 - '''~~Under development (10.02-02)~~'''	+	* <s>Votes should be changeable</s> - '''Done'''
	* 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

vdvsx: /* Automatic checks/Autobuilder */

2010-03-07T14:26:37Z

Automatic checks/Autobuilder

← Older revision		Revision as of 14:26, 7 March 2010
Line 7:		Line 7:

	== Automatic checks/Autobuilder ==		== Automatic checks/Autobuilder ==
-	* Bugtracker field - '''~~Under development (10.02-01)~~'''	+	* <s>Bugtracker field</s> - '''Done'''
-	* That the description field is not empty - '''~~Under development (10.02-01)~~'''	+	* <s>That the description field is not empty</s> - '''Done'''
	* 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

vdvsx at 15:44, 9 February 2010

2010-02-09T15:44:57Z

← Older revision		Revision as of 15:44, 9 February 2010
Line 7:		Line 7:

	== Automatic checks/Autobuilder ==		== Automatic checks/Autobuilder ==
-	* Bugtracker field	+	* Bugtracker field - '''Under development (10.02-01)'''
-	* That the description field is not empty	+	* That the description field is not empty - '''Under development (10.02-01)'''
	* 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.	+	* Changelog should be displayed - '''Under development (10.02-03)'''
	* 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.	+	* Votes should be changeable - '''Under development (10.02-02)'''
	* 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 his maintainers or by a member of the testing squad (demotions should be advertised in the testing squad list).	+	* Packages can be demoted at any time by his maintainers ('''Implemented''') or by a member of the testing squad (demotions should be advertised in the testing squad list).
	* 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.		* 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.

ossi1967: /* Testing Squad */

2010-02-02T09:58:19Z

Testing Squad

← Older revision		Revision as of 09:58, 2 February 2010
Line 87:		Line 87:
	* Can demote packages when there is known blockers.		* 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.
		+	* Can promote packages in speed promotion process [[User:ossi1967\|ossi1967]]

	=== Testing Squad mailing list ===		=== Testing Squad mailing list ===

ossi1967: /* Package Interface */ propose "speed promotion"

2010-02-02T09:57:27Z

Package Interface: propose "speed promotion"

← Older revision		Revision as of 09:57, 2 February 2010
Line 37:		Line 37:
	* 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).		* 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 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.		* 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 ===
		+	* Maintainer can request speed promotion through interface in well defined cases: critical bug in "Extras"-version needs urgent fix; only cosmetic changes (new translations, icons, package description,...);
		+	* 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]]

	== Check List ==		== Check List ==

jukey: /* Testing Squad mailing list */

2010-01-26T08:04:02Z

Testing Squad mailing list

← Older revision		Revision as of 08:04, 26 January 2010
Line 86:		Line 86:
	* 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 a automatic notification for each packages that enters testing, is demoted or is promoted.		* Receives a automatic notification for each packages that enters testing, is demoted or is promoted.
-	[[Category:QA]]	+	[[Category:Quality Assurance]]

jukey: /* Testing Squad mailing list */

2010-01-26T07:59:34Z

Testing Squad mailing list

← Older revision		Revision as of 07:59, 26 January 2010
Line 86:		Line 86:
	* 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 a automatic notification for each packages that enters testing, is demoted or is promoted.		* Receives a automatic notification for each packages that enters testing, is demoted or is promoted.
		+	[[Category:QA]]