BSP Test Plan - Revision history

Vineela Tummalapalli: /* Test Process */

2020-02-13T18:52:30Z

Test Process

← Older revision		Revision as of 18:52, 13 February 2020
Line 145:		Line 145:
	- Write the image to a bootable media (USB key, SD Card, etc.) using the dd command:		- Write the image to a bootable media (USB key, SD Card, etc.) using the dd command:
	'''$ sudo dd if=tmp/deploy/images/intel-corei7-64/core-image-base-intel-corei7-64.wic of=TARGET_DEVICE'''		'''$ sudo dd if=tmp/deploy/images/intel-corei7-64/core-image-base-intel-corei7-64.wic of=TARGET_DEVICE'''
			'''example with usb key connected: $ sudo dd if=tmp/deploy/images/intel-corei7-64/core-image-base-intel-corei7-64.wic of=/dev/sdb'''
	- Attach the bootable device to the DUT		- Attach the bootable device to the DUT
	- Turn the DUT on, and use its boot options to select the correct media for booting		- Turn the DUT on, and use its boot options to select the correct media for booting

Vineela Tummalapalli: /* Test Process */

2020-02-13T18:50:26Z

Test Process

← Older revision		Revision as of 18:50, 13 February 2020
Line 147:		Line 147:
	- Attach the bootable device to the DUT		- Attach the bootable device to the DUT
	- Turn the DUT on, and use its boot options to select the correct media for booting		- Turn the DUT on, and use its boot options to select the correct media for booting
	- By default ~~the~~ username is "root". (This is because the yocto image by default uses "debug-tweaks" feature)		- After the DUT boots to image in USB stick, the default username is "root". (This is because the yocto image by default uses "debug-tweaks" feature)
	- Ensure the device has a network connection and a valid IP address		- Ensure the device has a network connection and a valid IP address

Vineela Tummalapalli: /* Test Process */

2020-02-13T18:49:22Z

Test Process

← Older revision		Revision as of 18:49, 13 February 2020
Line 147:		Line 147:
	- Attach the bootable device to the DUT		- Attach the bootable device to the DUT
	- Turn the DUT on, and use its boot options to select the correct media for booting		- Turn the DUT on, and use its boot options to select the correct media for booting
			- By default the username is "root". (This is because the yocto image by default uses "debug-tweaks" feature)
	- Ensure the device has a network connection and a valid IP address		- Ensure the device has a network connection and a valid IP address

Sangeeta Jain: /* Test Process */

2020-01-23T23:18:32Z

Test Process

← Older revision		Revision as of 23:18, 23 January 2020
Line 209:		Line 209:
	7. Verify that all test cases PASSED if not raise bugs properly		7. Verify that all test cases PASSED if not raise bugs properly

	[Deprecated]		[Deprecated]
	Update results to corresponding Testopia Test Run		Update results to corresponding Testopia Test Run
	'''There is a script available to upload results form the log automatically on [[Qa-tools#Testopia_Update\|QA-Tools]] and follow this example [[Qa-tools#Update_a_Test_Run_by_ID\|Update TR by ID]]'''		'''There is a script available to upload results form the log automatically on [[Qa-tools#Testopia_Update\|QA-Tools]] and follow this example [[Qa-tools#Update_a_Test_Run_by_ID\|Update TR by ID]]'''

Sangeeta Jain: /* Test Process */

2020-01-23T23:17:40Z

Test Process

← Older revision		Revision as of 23:17, 23 January 2020
Line 204:		Line 204:
	'''example bitbake core-image-sato-sdk -c testimage -v'''		'''example bitbake core-image-sato-sdk -c testimage -v'''

	6. ~~Verify that all~~ test ~~cases PASSED if not raise bugs properly~~		6. Collect the test result from <build>/tmp/log/oeqa/testresults.json
			Note: Collect test results after one test run completed.

	7. Update results to corresponding Testopia Test Run		7. Verify that all test cases PASSED if not raise bugs properly

			[Deprecated]
			Update results to corresponding Testopia Test Run
	'''There is a script available to upload results form the log automatically on [[Qa-tools#Testopia_Update\|QA-Tools]] and follow this example [[Qa-tools#Update_a_Test_Run_by_ID\|Update TR by ID]]'''		'''There is a script available to upload results form the log automatically on [[Qa-tools#Testopia_Update\|QA-Tools]] and follow this example [[Qa-tools#Update_a_Test_Run_by_ID\|Update TR by ID]]'''

Sangeeta Jain: /* Scope */

2019-08-19T04:07:37Z

Scope

← Older revision		Revision as of 04:07, 19 August 2019
Line 64:		Line 64:
	** Network		** Network

	~~All~~ test ~~cases can be found here~~ <>		complete test steps of these manual tests are on poky repo under meta/lib/oeqa/manual/ <>

	* Automated Tests		* Automated Tests
Line 96:		Line 96:

	full code of this automated test are on poky repo under meta/lib/oeqa/runtime/cases <>		full code of this automated test are on poky repo under meta/lib/oeqa/runtime/cases <>


	= Test Strategy =		= Test Strategy =

Sangeeta Jain: /* Team members */

2019-08-19T04:03:24Z

Team members

← Older revision		Revision as of 04:03, 19 August 2019
Line 31:		Line 31:
	{\| style="border-spacing:0;margin:auto;width:6.925in;"		{\| style="border-spacing:0;margin:auto;width:6.925in;"
	\|-		\|-
	\| style="border-top:0.05pt solid #000000;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.0382in;" \| Yi ~~Zaho~~		\| style="border-top:0.05pt solid #000000;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.0382in;" \| Yi Zhao
	\| style="border:0.05pt solid #000000;padding:0.0382in;" \| Wind River		\| style="border:0.05pt solid #000000;padding:0.0382in;" \| Wind River
	\|-		\|-

Sangeeta Jain: /* Team members */

2019-08-19T04:02:59Z

Team members

← Older revision		Revision as of 04:02, 19 August 2019
Line 19:		Line 19:
	{\| style="border-spacing:0;margin:auto;width:6.925in;"		{\| style="border-spacing:0;margin:auto;width:6.925in;"
	\|-		\|-
	\| style="border-top:0.05pt solid #000000;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.0382in;" \| ~~José Pérez Carranza~~		\| style="border-top:0.05pt solid #000000;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.0382in;" \| Ee Peng Yeoh
	\| style="border:0.05pt solid #000000;padding:0.0382in;" \| Intel		\| style="border:0.05pt solid #000000;padding:0.0382in;" \| Intel
	\|-		\|-
Line 25:		Line 25:
	{\| style="border-spacing:0;margin:auto;width:6.925in;"		{\| style="border-spacing:0;margin:auto;width:6.925in;"
	\|-		\|-
	\| style="border-top:0.05pt solid #000000;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.0382in;" \| ~~Oscar Lopez Arandas~~		\| style="border-top:0.05pt solid #000000;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.0382in;" \| Sangeeta Jain
	\| style="border:0.05pt solid #000000;padding:0.0382in;" \| Intel		\| style="border:0.05pt solid #000000;padding:0.0382in;" \| Intel
	\|-		\|-
Line 35:		Line 35:
	\|-		\|-
	\|}		\|}


	= Scope =		= Scope =

Yeoh, Ee Peng at 07:24, 19 July 2019

2019-07-19T07:24:47Z

← Older revision		Revision as of 07:24, 19 July 2019
Line 179:		Line 179:
	if image is LSB		if image is LSB
	DISTRO ?= "poky-lsb"		DISTRO ?= "poky-lsb"
			3.9 Make sure conf only set DISTRO once, if DISTRO was set more than once, during testimage you could face error:
			> ERROR: Nothing PROVIDES 'core-image-lsb-sdk'
			> core-image-lsb-sdk was skipped: missing required distro feature 'pam'
			> (not in DISTRO_FEATURES)

	'''For releases before 2.3 also add'''		'''For releases before 2.3 also add'''
	TEST_SUITES = " auto"		TEST_SUITES = " auto"

Yeoh, Ee Peng: /* Reporting Process */

2019-03-20T05:52:55Z

Reporting Process

← Older revision		Revision as of 05:52, 20 March 2019
Line 243:		Line 243:

	1. Generate the report of pTests as follows:		1. Generate the report of pTests as follows:
	1.1 ~~Get~~ the current release ~~ptest log from the DUT.~~		1.1 Collect the testresults.json files for both current release (base) and previous release (target).
	~~1.2 Go to the [[Ptest/archive]] page~~ and ~~check the~~ previous release.		1.2 Use "resulttool report" to compute the ptest summary result using current release (base).
	1.~~3 From~~ the ~~previous release~~ ptest ~~page, get the previous~~ release ~~ptest log~~.		$ resulttool report <file_path_to_current_ptest_testresultsjson>
	~~1.4 Use the [[Qa-tools#Ptest_Parser\|ptest-parser]] script to generate the~~ report~~, this script generates a file called~~ <~~release~~>~~wiki.page. Inside the~~		1.3 Use "resulttool regression" to compute the ptest regression as below
	~~qa-tools/scripts folder, download both current and previous release ptest log, then execute~~ .~~/ptest-parser.py --help~~ to ~~check~~ the ~~arguments needed.~~		$ resulttool regression <file_path_to_current_ptest_testresultsjson> <file_path_to_previous_ptest_testresultsjson>
	~~Provide the arguments and execute~~ ptest~~-parser. (eg. ./ptest-parser.py -p ptest_2.4.2.rc2.txt -c ptest_2.4.3.rc2.txt --pre_commit~~		1.4 Copy and paste the report and regression report to wiki page https://wiki.yoctoproject.org/wiki/Ptest/archive
	~~342fbd6a3e57021c8e28b124b3adb241936f3d9d --pre_release 2.4.2.rc2 --curr_commit 7e7ee662f5dea4d090293045f7498093322802cc --curr_release 2.4.3.rc2).~~
	~~1.5 Create a wiki with the name '''Ptest_~~<~~commit-tested~~>~~'''~~
	1.6 Copy ~~the content of the content of '''<release>wiki.page'''~~ and paste ~~it on new wiki created.~~
	~~1.7 Upload~~ the ~~ptest log of current release~~ and ~~update the '''Ptest_<commit-tested>'''~~ wiki ~~with the link to the log.~~
	~~(eg. '~~https://wiki.yoctoproject.org/wiki/~~images/b/b4/Ptest_2.4.3.rc2.txt < FULL_LOG')~~
	~~1.8 Update the [[~~Ptest/archive~~]] wiki with the info of this new execution.~~
	~~1.9 Check each packages ptest for individual test that passed in previous release but failed in current release. Look at the 2 folder created: 'cur_log'~~
	~~and 'prev_log', inside contain files with ptest for each individual package. 'cur_log' contain ptest files from current release, 'prev_log' contain~~
	~~ptest files from previous release.~~
	~~Use git diff to identify individual test that passed in previous release but failed in current release, if there is a bug reported update the bug~~
	~~with comments that still present on current commit, if there is no bug created raise a new one.~~

	== Compliance ==		== Compliance ==