Yocto 2.1 Overall Test Plan - Revision history

Alexandru.c.georgescu: /* Reversion history */

2016-03-29T15:39:06Z

Reversion history

← Older revision		Revision as of 15:39, 29 March 2016
Line 3:		Line 3:
	! Version \|\| Modifier \|\| Comments		! Version \|\| Modifier \|\| Comments
	\|-		\|-
	\| 1.0 \|\| Alexandru Georgescu \|\| first draft		\| 2.1_M2 \|\| Alexandru Georgescu \|\| first draft
			\|-
			\| 2.1_M3.rc2 \|\| Alexandru Georgescu/ Jose Perez Carranza \|\| Test Plan review 3/29/2016
	\|}		\|}

	<!-- Editing tools below -->		<!-- Editing tools below -->
	<!-- The table can be edited with this tool : http://www.tablesgenerator.com/mediawiki_tables -->		<!-- The table can be edited with this tool : http://www.tablesgenerator.com/mediawiki_tables -->


	= Introduction =		= Introduction =

2016-03-29T15:30:53Z

Validation

← Older revision		Revision as of 15:30, 29 March 2016
Line 851:		Line 851:
	= Validation =		= Validation =
	*; Objective:		*; Objective:
	** Verify the correct functionality of [https://wiki.yoctoproject.org/wiki/Yocto_1.7_Features new] changes introduced in version ~~1.7~~ of the {{ns:4}}.		** Verify the correct functionality of [https://wiki.yoctoproject.org/wiki/Yocto_1.7_Features new] changes introduced in current version of the {{ns:4}}.

	*; Entry criteria:		*; Entry criteria:
	** The change is tracked by filling in the "QA Owner" field for the Medium+/High enhancements		** The change is tracked by filling in the "QA Owner" field for the Medium+/High enhancements
	** The change is prioritized in [https://bugzilla.yoctoproject.org/ Bugzilla]		** The change is prioritized in [https://bugzilla.yoctoproject.org/ Bugzilla]
	** Bugzilla entry has a target milestone within version ~~1.7~~		** Bugzilla entry has a target milestone within the current version
	** The change is documented or pointed out when no documentation is necessary (the doc flag is set accordingly)		** The change is documented or pointed out when no documentation is necessary (the doc flag is set accordingly)
	** Bug status is set to RESOLVED.		** Bug status is set to RESOLVED.

2016-03-29T15:22:41Z

Application Development Toolkit

← Older revision		Revision as of 15:22, 29 March 2016
Line 540:		Line 540:
	*Cross-toolchain install&compiling Test		*Cross-toolchain install&compiling Test
	*relocatable SDK		*relocatable SDK
			*extensible SDK (eSDK)
	*toolchain tarballs		*toolchain tarballs
	*yocto build tree		*yocto build tree

2016-03-29T15:21:21Z

Application Development Toolkit

← Older revision		Revision as of 15:21, 29 March 2016
Line 536:		Line 536:
	=== Developer Tools ===		=== Developer Tools ===
	==== Application Development Toolkit ====		==== Application Development Toolkit ====
	ADT testing includes tests for ~~ADT-installer,~~ meta-toolchain-sdk and user build sdk. It will be covered in Weekly and Fullpass testing.		ADT testing includes tests for meta-toolchain-sdk and user build sdk. It will be covered in Weekly and Fullpass testing.

	*Cross-toolchain install&compiling Test		*Cross-toolchain install&compiling Test
	*relocatable SDK		*relocatable SDK
	*ADT installer
	*toolchain tarballs		*toolchain tarballs
	*yocto build tree		*yocto build tree

2016-03-29T15:14:36Z

Distro Testing

← Older revision		Revision as of 15:14, 29 March 2016
Line 93:		Line 93:
	[TBD] - distribution support wiki needs to be updated		[TBD] - distribution support wiki needs to be updated

	The test run template for Distro testing, can be found in the [https://bugzilla.yoctoproject.org/~~tr_show_product~~.cgi?~~product_id~~=74 Automated Build testing Bugzilla product] in the master branch.		The test run template for Distro testing, can be found in the [https://bugzilla.yoctoproject.org/tr_show_plan.cgi?plan_id=147 Automated Build testing Bugzilla product] in the master branch.
	* [https://bugzilla.yoctoproject.org/tr_show_run.cgi?run_id=4083 Distro Template]		* [https://bugzilla.yoctoproject.org/tr_show_run.cgi?run_id=4083 Distro Template]

2016-02-26T12:32:33Z

Contrib repositories

← Older revision		Revision as of 12:32, 26 February 2016
Line 841:		Line 841:


	== ~~Contrib~~ repositories ==		== Test Automation contrib repositories ==

	*[[oe-selftest]]		*[[oe-selftest]]

2016-02-26T12:30:14Z

Autobuilder

← Older revision		Revision as of 12:30, 26 February 2016
Line 574:		Line 574:
	== Autobuilder ==		== Autobuilder ==

	More information can be found in the [[~~Autobuilder~~]] wiki.		More information can be found in the [[AutoBuilder]] wiki.

	== oe-selftest ==		== oe-selftest ==

2016-02-26T12:27:08Z

Sanity Testing

← Older revision		Revision as of 12:27, 26 February 2016
Line 494:		Line 494:

	==== Sanity Testing ====		==== Sanity Testing ====
	BSP Sanity testing is performed by the public [~~Autobuilder~~], where all the BSP artifacts are built and checked if they are built correctly. On public [[~~Autobuilder~~]], [[Image tests]] is being run also on the QEMU images as well.		BSP Sanity testing is performed by the public [[AutoBuilder]], where all the BSP artifacts are built and checked if they are built correctly. On public [[AutoBuilder]], [[Image tests]] is being run also on the QEMU images as well.

	==== Weekly Testing ====		==== Weekly Testing ====

2016-02-26T12:21:24Z

Build System

← Older revision		Revision as of 12:21, 26 February 2016
Line 57:		Line 57:
	Currently, [[oe-selftest]] covers all [[#Bitbake]], oe-core and [[#Metadata]] autoamted tests.		Currently, [[oe-selftest]] covers all [[#Bitbake]], oe-core and [[#Metadata]] autoamted tests.
	The Testopia template for oe-selftest is found in oe-core Bugzilla product:		The Testopia template for oe-selftest is found in oe-core Bugzilla product:
	* [https://bugzilla.yoctoproject.org/tr_show_run.cgi?run_id=5017 oe-core/oe-selftest ~~weekly~~]		* [https://bugzilla.yoctoproject.org/tr_show_run.cgi?run_id=5017 oe-core/oe-selftest Weekly Template]

	==== BitBake ====		==== BitBake ====
Line 83:		Line 83:

	==== Metadata ====		==== Metadata ====
	Testing the core metadata of the {{ns:4}} is mainly covered in the overall testing process, through other [[#Test Areas]] like [[#BitBake]] and [[#Toaster]] mentioned above. We also have ~~some~~ tests covering meta-yocto in the meta-yocto test run template, which we are running regularly:		Testing the core metadata of the {{ns:4}} is mainly covered in the overall testing process, through other [[#Test Areas]] like [[#BitBake]] and [[#Toaster]] mentioned above. We also have specific tests covering meta-yocto in the meta-yocto test run template, which we are running regularly at Full Pass:

	* [https://bugzilla.yoctoproject.org/tr_show_run.cgi?run_id=4855 Meta-yocto - Full Pass Template]		* [https://bugzilla.yoctoproject.org/tr_show_run.cgi?run_id=4855 Meta-yocto - Full Pass Template]

2016-02-26T12:11:55Z

Tasks

← Older revision		Revision as of 12:11, 26 February 2016
Line 33:		Line 33:
	Here is a list with all tasks identified by this testing plan.		Here is a list with all tasks identified by this testing plan.

	* ~~Testing~~		* General component testing
	* Bug and Feature reporting		* Bug and Feature reporting
	* Bug and Feature verification		* Bug and Feature verification
	* Test automation		* Test automation
	* Exploratory testing		* Exploratory testing
	* Creating testing plans for ~~specific~~ areas		* Creating testing plans for required areas
	* Review testing approaches with development peers		* Review testing approaches with development peers
	* Assign owners on major features		* Assign QA owners on major features

	= Testing Strategy =		= Testing Strategy =