Enabling Automation Test in Poky - Revision history

PaulEggleton: Replace old content with link to appropriate manual section

2014-06-16T12:03:17Z

Replace old content with link to appropriate manual section

← Older revision		Revision as of 12:03, 16 June 2014
Line 1:		Line 1:
	~~=== Enable Automation Test in Poky ===~~		Please see the [http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#performing-automated-runtime-testing Performing Automated Runtime Testing] section of the Yocto Project Development Manual.
	~~Currently we have implemented a handful automated sanity test cases in Poky (boot/ssh/dmesg/shutdown/zypper_help/zypper_search/rpm_query/compiler/connman). A user can follow~~ the ~~below steps to enable the runtime automation test~~:

	* Make sure your working tree has latest test code from master. This feature was not part of the 0.9 release (but will be included in 1.0)
	* Make sure your machine has the "expect" package installed. The package is necessary for testing. We will add a recipe for it later. Currently, you need install it by yourself. On Ubuntu host, you can use apt-get to install expect:
	~~<pre>~~
	~~$ apt-get install expect~~
	~~</pre>~~
	* Edit /etc/~~sudoers to allow the user run sudo without prompted for a password. For example, you can do like following for user "tester":~~
	~~<pre>~~
	~~$ cat~~ /~~etc/sudoers~~
	~~# /etc/sudoers~~
	#
	~~# This file MUST be edited with the 'visudo' command as root.~~
	#
	~~# See the man page for details on how to write a sudoers file.~~
	#
	....
	~~....~~
	~~....~~

	~~%tester ALL=(ALL) NOPASSWD: NOPASSWD: ALL~~
	</~~pre>~~
	* Instead of requiring sudo access, you can run the poky-gen-tapdevs script from a build of meta-ide-support or a Poky toolchain install. This is recommended for more security-conscious environments. The script will create and set up networking for one or more tap devices that will be used automatically by the poky-qemu script if detected, and it will no longer require root access.
	* Typically, you need a X environment to start QEMU. You can use your desktop's DISPLAY. Or, alternatively, you can install vncserver, and startup a X environment in localhost:x.0. (x can be 1, 2, 3.....n)
	* For the VNC setup, the following xstartup script is known to work for an openSUSE 11.2 host:
	~~<pre>~~
	#!/~~bin~~/sh

	~~xrdb $HOME/.Xresources~~
	~~xsetroot~~ -~~solid grey~~
	~~xhost +~~
	~~xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &~~
	~~twm &~~
	</~~pre>~~
	* For the VNC setup, you will also want to put the following in ~/.twmrc, which allows windows to be placed automatically.
	~~<pre>~~
	~~RandomPlacement~~
	~~</pre>~~
	* You need set "IMAGETEST" to "qemu" in build/conf/local.conf
	~~<pre>~~
	~~$ cat local.conf~~
	~~.....~~
	~~# Set IMAGETEST to qemu if you want to build testcases and start~~
	~~# testing in qemu after do_rootfs.~~
	~~IMAGETEST = "qemu"~~
	~~.....~~
	~~</pre>~~
	* Select the test cases you want to run, by default all cases in sanity scenario(check the files under scripts/qemuimage-~~tests/sanity) will be run. If you want to choose only one or not all cases for testing, you can uncomment and edit TEST_SCEN in local~~.~~conf:~~
	~~<pre>~~
	# ~~By default test cases in sanity suite will be ran. If you want to run other~~
	~~# test suite or specific test case(e.g. bat or boot test case under sanity suite),~~
	~~# list them like following.~~
	~~TEST_SCEN = "sanity:boot sanity:ssh sanity:dmesg"~~
	~~</pre>~~
	* Then you can run "bitbake poky-~~image~~-~~xxx" (xxx can be minimal, sato, sdk, lsb). After the kernel/image are generated, you need run "bitbake poky~~-~~image-xxx -c qemuimagetest" or "bitbake poky-image-xxx -c qemuimagetest_standalone". It will trigger automation test and you will get~~ the ~~result after a while. qemuimagetest will re-generate rootfs image and qemuimagetest_standalone will use existing rootfs images under $DEPLOY_DIR/images~~.

Jiajun: /* Enable Automation Test in Poky */

2011-01-11T08:17:37Z

Enable Automation Test in Poky

← Older revision		Revision as of 08:17, 11 January 2011
Line 47:		Line 47:
	.....		.....
	</pre>		</pre>
	* Select the test cases you want to run, by default all cases in sanity scenario(check the files under scripts/qemuimage-tests/sanity) will be run. If you want to choose only one or not all cases for testing, you can edit TEST_SCEN in local.conf:		* Select the test cases you want to run, by default all cases in sanity scenario(check the files under scripts/qemuimage-tests/sanity) will be run. If you want to choose only one or not all cases for testing, you can uncomment and edit TEST_SCEN in local.conf:
	<pre>		<pre>
	# By default test cases in sanity suite will be ran. If you want to run other		# By default test cases in sanity suite will be ran. If you want to run other
	# test suite or specific test case(e.g. bat or boot test case under sanity suite),		# test suite or specific test case(e.g. bat or boot test case under sanity suite),
	# list them like following.		# list them like following.
	#TEST_SCEN = "sanity:boot sanity:ssh sanity:dmesg"		TEST_SCEN = "sanity:boot sanity:ssh sanity:dmesg"
	</pre>		</pre>
	* Then you can run "bitbake poky-image-xxx" (xxx can be minimal, sato, sdk, lsb). After the kernel/image are generated, you need run "bitbake poky-image-xxx -c qemuimagetest" or "bitbake poky-image-xxx -c qemuimagetest_standalone". It will trigger automation test and you will get the result after a while. qemuimagetest will re-generate rootfs image and qemuimagetest_standalone will use existing rootfs images under $DEPLOY_DIR/images.		* Then you can run "bitbake poky-image-xxx" (xxx can be minimal, sato, sdk, lsb). After the kernel/image are generated, you need run "bitbake poky-image-xxx -c qemuimagetest" or "bitbake poky-image-xxx -c qemuimagetest_standalone". It will trigger automation test and you will get the result after a while. qemuimagetest will re-generate rootfs image and qemuimagetest_standalone will use existing rootfs images under $DEPLOY_DIR/images.

Jiajun: /* Enable Automation Test in Poky */

2011-01-11T08:17:12Z

Enable Automation Test in Poky

← Older revision		Revision as of 08:17, 11 January 2011
Line 1:		Line 1:
	=== Enable Automation Test in Poky ===		=== Enable Automation Test in Poky ===
	Currently we have implemented a handful automated sanity test cases in Poky (boot/ssh/dmesg/shutdown). A user can follow the below steps to enable the runtime automation test:		Currently we have implemented a handful automated sanity test cases in Poky (boot/ssh/dmesg/shutdown/zypper_help/zypper_search/rpm_query/compiler/connman). A user can follow the below steps to enable the runtime automation test:

	* Make sure your working tree has latest test code from master. This feature was not part of the 0.9 release (but will be included in 1.0)		* Make sure your working tree has latest test code from master. This feature was not part of the 0.9 release (but will be included in 1.0)
Line 47:		Line 47:
	.....		.....
	</pre>		</pre>
	* Then you can run "bitbake poky-image-xxx" (xxx can be minimal, sato, sdk). After the kernel/image are generated, you need run "bitbake poky-image-xxx -c qemuimagetest". It will trigger automation test and you will get the result after a while. :)		* Select the test cases you want to run, by default all cases in sanity scenario(check the files under scripts/qemuimage-tests/sanity) will be run. If you want to choose only one or not all cases for testing, you can edit TEST_SCEN in local.conf:
			<pre>
			# By default test cases in sanity suite will be ran. If you want to run other
			# test suite or specific test case(e.g. bat or boot test case under sanity suite),
			# list them like following.
			#TEST_SCEN = "sanity:boot sanity:ssh sanity:dmesg"
			</pre>
			* Then you can run "bitbake poky-image-xxx" (xxx can be minimal, sato, sdk, lsb). After the kernel/image are generated, you need run "bitbake poky-image-xxx -c qemuimagetest" or "bitbake poky-image-xxx -c qemuimagetest_standalone". It will trigger automation test and you will get the result after a while. qemuimagetest will re-generate rootfs image and qemuimagetest_standalone will use existing rootfs images under $DEPLOY_DIR/images.

Sgarman at 18:53, 14 December 2010

2010-12-14T18:53:11Z

← Older revision		Revision as of 18:53, 14 December 2010
Line 1:		Line 1:
	=== Enable Automation Test in Poky ===		=== Enable Automation Test in Poky ===
	Currently we have implemented ~~two~~ automated sanity test cases in Poky. ~~User~~ can follow below steps to enable the automation test:		Currently we have implemented a handful automated sanity test cases in Poky (boot/ssh/dmesg/shutdown). A user can follow the below steps to enable the runtime automation test:

	* Make sure your working tree has latest test code. ~~The first sanity test implementation is checked~~ in ~~poky master tree as commit, '''fd1d661b391dfad1edaac937a17c1165f635031a~~.		* Make sure your working tree has latest test code from master. This feature was not part of the 0.9 release (but will be included in 1.0)
	* Make sure your machine has ~~package~~ "expect" installed. The package is necessary for testing. We will add a recipe for it later. Currently, you need install it by yourself. On Ubuntu host, you can use apt-get to install expect:		* Make sure your machine has the "expect" package installed. The package is necessary for testing. We will add a recipe for it later. Currently, you need install it by yourself. On Ubuntu host, you can use apt-get to install expect:
	<pre>		<pre>
	$ apt-get install expect		$ apt-get install expect
Line 22:		Line 22:
	%tester ALL=(ALL) NOPASSWD: NOPASSWD: ALL		%tester ALL=(ALL) NOPASSWD: NOPASSWD: ALL
	</pre>		</pre>
	* Instead of requiring sudo access, you can run the poky-gen-tapdevs script from a build of meta-ide-support or a Poky toolchain install ~~in /opt/poky~~. The script will create and set up networking for one or more tap devices that will be used automatically by the poky-qemu script if detected.		* Instead of requiring sudo access, you can run the poky-gen-tapdevs script from a build of meta-ide-support or a Poky toolchain install. This is recommended for more security-conscious environments. The script will create and set up networking for one or more tap devices that will be used automatically by the poky-qemu script if detected, and it will no longer require root access.
	* Typically, you need a X environment to start QEMU. You can use your desktop's DISPLAY. Or, alternatively, you can install vncserver, and startup a X environment in localhost:x.0. (x can be 1, 2, 3.....n)		* Typically, you need a X environment to start QEMU. You can use your desktop's DISPLAY. Or, alternatively, you can install vncserver, and startup a X environment in localhost:x.0. (x can be 1, 2, 3.....n)
	* For the VNC setup, the following xstartup script is known to work for an openSUSE 11.2 host:		* For the VNC setup, the following xstartup script is known to work for an openSUSE 11.2 host:

Sgarman: Added some important details to sanity test automation regarding VNC setup

2010-11-12T07:11:13Z

Added some important details to sanity test automation regarding VNC setup

@@ Line 22: / Line 22: @@
 %tester ALL=(ALL) NOPASSWD: NOPASSWD: ALL
 </pre>
 * Typically, you need a X environment to start QEMU. You can use your desktop's DISPLAY. Or, alternatively, you can install vncserver, and startup a X environment in localhost:x.0. (x can be 1, 2, 3.....n)
 * You need set "IMAGETEST" to "qemu" in build/conf/local.conf
 <pre>

Scottrif: Created page with '=== Enable Automation Test in Poky === Currently we have implemented two automated sanity test cases in Poky. User can follow below steps to enable the automation test: * Make s…'

2010-10-22T22:35:58Z

Created page with '=== Enable Automation Test in Poky === Currently we have implemented two automated sanity test cases in Poky. User can follow below steps to enable the automation test: * Make s…'

New page

=== Enable Automation Test in Poky ===
Currently we have implemented two automated sanity test cases in Poky. User can follow below steps to enable the automation test:

* Make sure your working tree has latest test code. The first sanity test implementation is checked in poky master tree as commit, '''fd1d661b391dfad1edaac937a17c1165f635031a.
* Make sure your machine has package "expect" installed. The package is necessary for testing. We will add a recipe for it later. Currently, you need install it by yourself. On Ubuntu host, you can use apt-get to install expect:
<pre>
$ apt-get install expect
</pre>
* Edit /etc/sudoers to allow the user run sudo without prompted for a password. For example, you can do like following for user "tester":
<pre>
$ cat /etc/sudoers
# /etc/sudoers
#
# This file MUST be edited with the 'visudo' command as root.
#
# See the man page for details on how to write a sudoers file.
#
....
....
....

%tester ALL=(ALL) NOPASSWD: NOPASSWD: ALL
</pre>
* Typically, you need a X environment to start QEMU. You can use your desktop's DISPLAY. Or, alternatively, you can install vncserver, and startup a X environment in localhost:x.0. (x can be 1, 2, 3.....n)
* You need set "IMAGETEST" to "qemu" in build/conf/local.conf
<pre>
$ cat local.conf
.....
# Set IMAGETEST to qemu if you want to build testcases and start
# testing in qemu after do_rootfs.
IMAGETEST = "qemu"
.....
</pre>
* Then you can run "bitbake poky-image-xxx" (xxx can be minimal, sato, sdk). After the kernel/image are generated, you need run "bitbake poky-image-xxx -c qemuimagetest". It will trigger automation test and you will get the result after a while. :)