Yocto 1.6 meta-intel testing plan - Revision history

Alexandru.c.georgescu: /* Test Areas */

2013-12-13T18:38:16Z

Test Areas

← Older revision		Revision as of 18:38, 13 December 2013
Line 12:		Line 12:
	* emenlow		* emenlow
	* crownbay		* crownbay
			* minnowboard
	* fri2		* fri2
	* nuc		* nuc

Alexandru.c.georgescu: /* Test Areas */

2013-12-04T12:03:55Z

Test Areas

← Older revision		Revision as of 12:03, 4 December 2013
Line 5:		Line 5:
	The meta-intel testing is being part of the [https://wiki.yoctoproject.org/wiki/Yocto_1.6_Overall_Test_Plan#Target_System Target System] test are within Yocto 1.6 Overall Testing Plan.		The meta-intel testing is being part of the [https://wiki.yoctoproject.org/wiki/Yocto_1.6_Overall_Test_Plan#Target_System Target System] test are within Yocto 1.6 Overall Testing Plan.
	The test cases that we run are available on [https://bugzilla.yoctoproject.org/tr_show_product.cgi Testopia]. There, you can browse to the BSPs component, select the “master branch” [https://bugzilla.yoctoproject.org/tr_show_plan.cgi?plan_id=18 testing plan] and then access the “Test Cases” panel to view all the test cases available. They are used for testing QEMU, core BSPs and meta-intel BSPs.		The test cases that we run are available on [https://bugzilla.yoctoproject.org/tr_show_product.cgi Testopia]. There, you can browse to the BSPs component, select the “master branch” [https://bugzilla.yoctoproject.org/tr_show_plan.cgi?plan_id=18 testing plan] and then access the “Test Cases” panel to view all the test cases available. They are used for testing QEMU, core BSPs and meta-intel BSPs.
	To organize them, we divided them into test runs templates (check the “Test runs” panel and filter by TEMPLATE) and then create new test runs based on them for each build that we need.		To organize them, we divided them into test runs templates (check the “Test runs” panel and filter by TEMPLATE) and then create new test runs based on them for each build that we need.

			As a reminder, the [[Testopia]] wiki have all the information needed for working with [[Testopia]].

	The target machines tested are:		The target machines tested are:

Alexandru.c.georgescu: /* Test Areas */

2013-12-04T12:01:47Z

Test Areas

← Older revision		Revision as of 12:01, 4 December 2013
Line 4:		Line 4:
	=Test Areas =		=Test Areas =
	The meta-intel testing is being part of the [https://wiki.yoctoproject.org/wiki/Yocto_1.6_Overall_Test_Plan#Target_System Target System] test are within Yocto 1.6 Overall Testing Plan.		The meta-intel testing is being part of the [https://wiki.yoctoproject.org/wiki/Yocto_1.6_Overall_Test_Plan#Target_System Target System] test are within Yocto 1.6 Overall Testing Plan.
	~~All the~~ test cases that are ~~being run can be found by accessing [~~[Testopia]] and ~~browsing~~ to the ~~BSP component from it~~. ~~Details on using Testopia~~, ~~how to access the~~ test runs and test ~~cases is available in the [[Testopia]] wiki~~.		The test cases that we run are available on [https://bugzilla.yoctoproject.org/tr_show_product.cgi Testopia]. There, you can browse to the BSPs component, select the “master branch” [https://bugzilla.yoctoproject.org/tr_show_plan.cgi?plan_id=18 testing plan] and then access the “Test Cases” panel to view all the test cases available. They are used for testing QEMU, core BSPs and meta-intel BSPs.
			To organize them, we divided them into test runs templates (check the “Test runs” panel and filter by TEMPLATE) and then create new test runs based on them for each build that we need.

	The target machines tested are:		The target machines tested are:

Alexandru.c.georgescu at 11:40, 4 December 2013

2013-12-04T11:40:47Z

← Older revision		Revision as of 11:40, 4 December 2013
Line 1:		Line 1:
	~~1.6~~ meta-intel ~~testing plan~~		= Objectives =
			The test process is mainly focused to track and review the quality and performance of the meta-intel BSPs.

			=Test Areas =
	[https://wiki.yoctoproject.org/wiki/~~Meta-intel_Release_Process release process~~]		The meta-intel testing is being part of the [https://wiki.yoctoproject.org/wiki/Yocto_1.6_Overall_Test_Plan#Target_System Target System] test are within Yocto 1.6 Overall Testing Plan.
			All the test cases that are being run can be found by accessing [[Testopia]] and browsing to the BSP component from it. Details on using Testopia, how to access the test runs and test cases is available in the [[Testopia]] wiki.


	target machines		The target machines tested are:
	* emenlow		* emenlow
	* crownbay		* crownbay
Line 13:		Line 15:
	* sugarbay		* sugarbay
	* crystalforest		* crystalforest


	~~= Objectives =~~
	~~The test process is mainly focused to track and review the quality and performance of the meta-intel BSPs.~~

	~~=Test Areas =~~
	~~The meta-intel testing is being part of the [https://wiki.yoctoproject.org/wiki/Yocto_1.6_Overall_Test_Plan#Target_System Target System] testing are within Yocto 1.6 Overall Testing Plan.~~
	~~All the test cases that are being run can be found by accessing [[Testopia]] and browsing to the BSP component from it. Details on using testopia cen be found here~~


	= Test Cycle =		= Test Cycle =
	The testing of meta-intel BSPs is performed on every Full pass, Release Candidate or Release test according to the [[Yocto 1.6 Schedule]]. meta-intel BSPs are not covered in the weekly testing.		The testing of meta-intel BSPs is performed on every Full pass, Release Candidate or Release test according to the [[Yocto 1.6 Schedule]]. meta-intel BSPs are not covered in the weekly testing.
	Details on the Full Pass, Release Candidate or Release Test can be found in the Test Cycle section in the [https://wiki.yoctoproject.org/wiki/Yocto_1.6_Overall_Test_Plan#Test_Cycle Yocto Overall 1.6 Test Plan]		Details on the Full Pass, Release Candidate or Release Test can be found in the Test Cycle section in the [https://wiki.yoctoproject.org/wiki/Yocto_1.6_Overall_Test_Plan#Test_Cycle Yocto Overall 1.6 Test Plan]. In the [[Meta-intel Release Process]] is detailed the release process of meta-intel.

	= Test Automation =		= Test Automation =
	The plan for 1.6 HW automation is detailed in the HW automation bug [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1596 1596]		The plan for 1.6 HW automation is detailed in the HW automation bug [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1596 1596].

Alexandru.c.georgescu at 09:51, 4 December 2013

2013-12-04T09:51:33Z

← Older revision		Revision as of 09:51, 4 December 2013
Line 13:		Line 13:
	* sugarbay		* sugarbay
	* crystalforest		* crystalforest


			= Objectives =
			The test process is mainly focused to track and review the quality and performance of the meta-intel BSPs.

			=Test Areas =
			The meta-intel testing is being part of the [https://wiki.yoctoproject.org/wiki/Yocto_1.6_Overall_Test_Plan#Target_System Target System] testing are within Yocto 1.6 Overall Testing Plan.
			All the test cases that are being run can be found by accessing [[Testopia]] and browsing to the BSP component from it. Details on using testopia cen be found here


			= Test Cycle =
			The testing of meta-intel BSPs is performed on every Full pass, Release Candidate or Release test according to the [[Yocto 1.6 Schedule]]. meta-intel BSPs are not covered in the weekly testing.
			Details on the Full Pass, Release Candidate or Release Test can be found in the Test Cycle section in the [https://wiki.yoctoproject.org/wiki/Yocto_1.6_Overall_Test_Plan#Test_Cycle Yocto Overall 1.6 Test Plan]

			= Test Automation =
			The plan for 1.6 HW automation is detailed in the HW automation bug [https://bugzilla.yoctoproject.org/show_bug.cgi?id=1596 1596]

Alexandru.c.georgescu: Created page with "1.6 meta-intel testing plan [https://wiki.yoctoproject.org/wiki/Meta-intel_Release_Process release process] target machines * emenlow * crownbay * fri2 * nuc * jasperforest *..."

2013-12-04T09:14:22Z

Created page with "1.6 meta-intel testing plan [https://wiki.yoctoproject.org/wiki/Meta-intel_Release_Process release process] target machines * emenlow * crownbay * fri2 * nuc * jasperforest *..."

New page

1.6 meta-intel testing plan

[https://wiki.yoctoproject.org/wiki/Meta-intel_Release_Process release process]

target machines
* emenlow
* crownbay
* fri2
* nuc
* jasperforest
* sugarbay
* crystalforest