Extensible SDK Test Plan (eSDK) - Revision history

Libby: /* Test automation */

2017-09-26T19:50:41Z

Test automation

← Older revision		Revision as of 19:50, 26 September 2017
Line 102:		Line 102:
	- poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.testdata.jason		- poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.testdata.jason

	5. Give execution permissions to sh files ~~and rename~~ files		5. Give execution permissions to sh files. Rename files, only if it asks.
	$ chmod +x *.sh		$ chmod +x *.sh
	$ for file in <RELEASE>; do mv "$file" "${file/<RELEASE>/<RELEASE>+snapshot}"; done		$ for file in <RELEASE>; do mv "$file" "${file/<RELEASE>/<RELEASE>+snapshot}"; done

Jose G Perez Carranza: /* Test automation */

2017-08-30T16:55:03Z

Test automation

← Older revision		Revision as of 16:55, 30 August 2017
Line 70:		Line 70:
	3. Build eSDK intaller		3. Build eSDK intaller
	$ bitbake core-image-minimal -c populate_sdk_ext -v		$ bitbake core-image-minimal -c populate_sdk_ext -v

	4. Execute the tests		4. Execute the tests
	$ bitbake core-image-minimal -c testsdkext		$ bitbake core-image-minimal -c testsdkext
Line 101:		Line 101:
	- poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.sh		- poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.sh
	- poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.testdata.jason		- poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.testdata.jason
	~~- x86_64-nativesdk-libc.tar.bz2~~
	~~- x86_64-nativesdk-libc.target.manifest~~
	~~- x86_64-nativesdk-libc.testdata.json~~

	~~$ wget <AB_LINK>/buildtools/<ARTIFACTS_NEEDED>~~		5. Give execution permissions to sh files and rename files
	~~NOTE: All the artifacts that should be downloaded are:~~
	~~- x86_64-buildtools-nativesdk-standalone-2.3.host.manifest~~
	~~- x86_64-buildtools-nativesdk-standalone-2.3.sh~~
	~~- x86_64-buildtools-nativesdk-standalone-2.3.target.manifest~~
	~~- x86_64-buildtools-nativesdk-standalone-2.3.testdata.json~~

	5. Give execution permissions to sh files
	$ chmod +x *.sh		$ chmod +x *.sh
			$ for file in <RELEASE>; do mv "$file" "${file/<RELEASE>/<RELEASE>+snapshot}"; done
			Example execute below command:
			$ for file in 2.3; do mv "$file" "${file/2.3/2.3+snapshot}"; done

	6. Go back to poky build folder "poky/build-pre-built"		6. Go back to poky build folder "poky/build-pre-built"
	$ cd -		$ cd -

	7. Execute the test		7. Prepare the environment to execute tests
			$ bitbake libxml2

			8. Execute the test
	$ bitbake core-image-minimal -c testsdkext		$ bitbake core-image-minimal -c testsdkext

	8. All test should be PASSED		9. All test should be PASSED

			NOTE: There are 4 combinations of tests that should be executed
			- qemux86 + minimal --> (poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext*)
			- qemux86 + sato --> (poky-glibc-x86_64-core-image-sato-i586-toolchain-ext*)
			- qemux86-64 + minimal --> (poky-glibc-x86_64-core-image-minimal-core2-64-toolchain-ext*)
			- qemux86-64 + sato --> (poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext*)

	* Test eSDK as part of the oe-selftest suite		* Test eSDK as part of the oe-selftest suite
Line 134:		Line 135:
	3. Execute the tests		3. Execute the tests
	$ oe-selftest -r eSDK		$ oe-selftest -r eSDK

	4. All test cases should be PASS		4. All test cases should be PASS

Jose G Perez Carranza: /* Test automation */

2017-08-28T15:30:03Z

Test automation

← Older revision		Revision as of 15:30, 28 August 2017
Line 72:		Line 72:

	4. Execute the tests		4. Execute the tests
	$ bitbake core image minimal -c testsdkext		$ bitbake core-image-minimal -c testsdkext

	5. All test should be PASSED		5. All test should be PASSED
Line 119:		Line 119:

	7. Execute the test		7. Execute the test
	$ bitbake core image minimal -c testsdkext		$ bitbake core-image-minimal -c testsdkext

	8. All test should be PASSED		8. All test should be PASSED

Jose G Perez Carranza: /* Test automation */

2017-08-25T19:07:35Z

Test automation

← Older revision		Revision as of 19:07, 25 August 2017
Line 91:		Line 91:
	4. Download artifacts form AB under new folder created		4. Download artifacts form AB under new folder created
	$ cd tmp/deploy/sdk		$ cd tmp/deploy/sdk
	$ wget <AB_LINK>/toolchain/x86_64/~~poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.target.manifest~~		$ wget <AB_LINK>/toolchain/x86_64/<ARTIFACTS_NEEDED>

	Example:		Example:
Line 101:		Line 101:
	- poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.sh		- poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.sh
	- poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.testdata.jason		- poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.testdata.jason
			- x86_64-nativesdk-libc.tar.bz2
			- x86_64-nativesdk-libc.target.manifest
			- x86_64-nativesdk-libc.testdata.json

	5. ~~Give execution permissions to~~ sh ~~file~~		$ wget <AB_LINK>/buildtools/<ARTIFACTS_NEEDED>
	~~$ chmod +x poky~~-~~glibc~~-~~x86_64~~-~~core~~-~~image~~-~~minimal~~-~~i586~~-~~toolchain~~-~~ext~~-2.3.sh		NOTE: All the artifacts that should be downloaded are:
			- x86_64-buildtools-nativesdk-standalone-2.3.host.manifest
			- x86_64-buildtools-nativesdk-standalone-2.3.sh
			- x86_64-buildtools-nativesdk-standalone-2.3.target.manifest
			- x86_64-buildtools-nativesdk-standalone-2.3.testdata.json

			5. Give execution permissions to sh files
			$ chmod +x *.sh

	6. Go back to poky build folder "poky/build-pre-built"		6. Go back to poky build folder "poky/build-pre-built"

Jose G Perez Carranza: /* Test automation */

2017-08-25T15:55:12Z

Test automation

← Older revision		Revision as of 15:55, 25 August 2017
Line 112:		Line 112:

	8. All test should be PASSED		8. All test should be PASSED


			* Test eSDK as part of the oe-selftest suite

			1. Under poky/ do another build folder different from the previous scenario
			$ source oe-init-build-env build-esdk-selftest

			2. Avoid Sanity Distro validation
			$ echo 'SANITY_TESTED_DISTROS = ""' >> conf/local.conf

			3. Execute the tests
			$ oe-selftest -r eSDK

			4. All test cases should be PASS

	== Test Approach ==		== Test Approach ==

Jose G Perez Carranza: /* Test automation */

2017-08-25T13:05:55Z

Test automation

← Older revision		Revision as of 13:05, 25 August 2017
Line 56:		Line 56:

	== Test automation ==		== Test automation ==

			Currently the execution of the cases is using "testsdkext" automation below are the three scenarios that should be tested

			* Test Building the eSDK installer:

			1. Clone poky and source the environment
			$ source oe-init-build-env

			2. Add proper configuration to local.conf
			$ echo 'SDK_EXT_TYPE = "minimal"' >> conf/local.conf
			$ echo 'INHERIT += "testsdk"' >> conf/local.conf

			3. Build eSDK intaller
			$ bitbake core-image-minimal -c populate_sdk_ext -v

			4. Execute the tests
			$ bitbake core image minimal -c testsdkext

			5. All test should be PASSED


			* Test using Pre-Built SDK Installers:

			1. Under poky/ do another build folder different from the previous scenario
			$ source oe-init-build-env build-pre-built

			2. Add proper configuration to local.conf
			$ echo 'SDK_EXT_TYPE = "minimal"' >> conf/local.conf
			$ echo 'INHERIT += "testsdk"' >> conf/local.conf

			3. Create sdk directory
			$ mkdir -p tmp/deploy/sdk

			4. Download artifacts form AB under new folder created
			$ cd tmp/deploy/sdk
			$ wget <AB_LINK>/toolchain/x86_64/poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.target.manifest

			Example:
			$ wget https://autobuilder.yocto.io/pub/releases/yocto-2.4_M3.rc1/toolchain/x86_64/poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.host.manifest

			NOTE: All the artifacts that should be downloaded are:
			- poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.target.manifest
			- poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.host.manifest
			- poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.sh
			- poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.testdata.jason

			5. Give execution permissions to sh file
			$ chmod +x poky-glibc-x86_64-core-image-minimal-i586-toolchain-ext-2.3.sh

			6. Go back to poky build folder "poky/build-pre-built"
			$ cd -

			7. Execute the test
			$ bitbake core image minimal -c testsdkext

			8. All test should be PASSED

	== Test Approach ==		== Test Approach ==

Francisco Pedraza: /* Tools */

2017-01-16T18:09:51Z

Tools

← Older revision		Revision as of 18:09, 16 January 2017
Line 198:		Line 198:

	=Tools=		=Tools=
			<p> Software Development Kit </p>

	= Release Criteria/ Exit Criteria =		= Release Criteria/ Exit Criteria =

Francisco Pedraza: /* Scope */

2017-01-16T18:03:06Z

Scope

← Older revision		Revision as of 18:03, 16 January 2017
Line 43:		Line 43:
	* Install additional SDK components.		* Install additional SDK components.
	* Locating Pre-Built SDK Installers.		* Locating Pre-Built SDK Installers.
	*
	<p><b>Node.js</b></p>		<p><b>Node.js</b></p>
	* Add Node.js Modules		* Add Node.js Modules

Francisco Pedraza: /* Risk Assumptions */

2016-06-23T16:20:38Z

Risk Assumptions

← Older revision		Revision as of 16:20, 23 June 2016
Line 195:		Line 195:

	=Risk Assumptions=		=Risk Assumptions=
			* The complete features will not be tested now, as per the automation is in process now.

	=Tools=		=Tools=

Francisco Pedraza: /* Requirements */

2016-06-23T16:19:17Z

Requirements

← Older revision		Revision as of 16:19, 23 June 2016
Line 94:		Line 94:
	<p>[https://bugzilla.yoctoproject.org/show_bug.cgi?id=8975 8975] As a developer I want to be able to validate the way how to detect recipe problems where it can become host-dependant. - [https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=1485 Test Case 1485]</p>		<p>[https://bugzilla.yoctoproject.org/show_bug.cgi?id=8975 8975] As a developer I want to be able to validate the way how to detect recipe problems where it can become host-dependant. - [https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=1485 Test Case 1485]</p>
	<p>[https://bugzilla.yoctoproject.org/show_bug.cgi?id=6658 6658] As a developer I want to be able to enable kernel development from devtool. - [https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=1486 Test Case 1486]</p>		<p>[https://bugzilla.yoctoproject.org/show_bug.cgi?id=6658 6658] As a developer I want to be able to enable kernel development from devtool. - [https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=1486 Test Case 1486]</p>
			<p>[https://bugzilla.yoctoproject.org/show_bug.cgi?id=8883 8883] As a developer I want to be able to update eSDK. - [https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=1487 Test Case 1487]</p>
	==HW Requirements==		==HW Requirements==
	* Any machine able to build.		* Any machine able to build.