Jose G Perez Carranza at 16:03, 8 March 2017

2017-03-08T16:03:13Z

← Older revision		Revision as of 16:03, 8 March 2017
Line 96:		Line 96:
	TEST_SERVER_IP = "HOST ip" --> IP of the machine being used to launch tests		TEST_SERVER_IP = "HOST ip" --> IP of the machine being used to launch tests
	TEST_TARGET_IP = "DUT ip" --> IP of the device under test		TEST_TARGET_IP = "DUT ip" --> IP of the device under test

			For releases before 2.3 also add

	TEST_SUITES = " auto"		TEST_SUITES = " auto"

Jair Gonzalez at 21:44, 27 October 2016

2016-10-27T21:44:24Z

← Older revision		Revision as of 21:44, 27 October 2016
Line 102:		Line 102:

	<p>		<p>
	5~~. In the repository designed to execute testimage, edit bblayers.conf PATH: ~/poky-test/build/conf~~		5. In ~/poky-test/build directory, in command line, type the following commands:
	~~</p>~~
	~~<ul><li>in " BBLAYERS ?= " \ " section add "meta-selftest" respecting the pattern from above</li></ul>~~

	~~<p>~~
	6. In ~/poky-test/build directory, in command line, type the following commands:
	</p>		</p>
	<pre>		<pre>
Line 119:		Line 114:

	<p>		<p>
	7. In ~/poky-test/build directory, start the testimage execution by typing the following command:		6. In ~/poky-test/build directory, start the testimage execution by typing the following command:
	</p>		</p>
	<pre>$ bitbake core-image-sato-sdk -c testimage</pre>		<pre>$ bitbake core-image-sato-sdk -c testimage</pre>

Jair Gonzalez: Editing page title to better reflect its content.

2016-10-27T21:40:52Z

Editing page title to better reflect its content.

← Older revision		Revision as of 21:40, 27 October 2016
Line 1:		Line 1:
	<h2>'''~~Additional~~ Steps for Automated Testing on QEMU'''</h2>		<h2>'''Steps for Automated Testing on QEMU'''</h2>

	<p>		<p>

Jair Gonzalez: Jair Gonzalez moved page Additional Steps for Automated Testing on QEMU to Steps for Automated Testing on QEMU: Changing the title of the page to better reflect its content, as not only additional steps for automated testing are mentioned in it...

2016-10-27T21:38:09Z

Jair Gonzalez moved page Additional Steps for Automated Testing on QEMU to Steps for Automated Testing on QEMU: Changing the title of the page to better reflect its content, as not only additional steps for automated testing are mentioned in it...

← Older revision	Revision as of 21:38, 27 October 2016
(No difference)

Jair Gonzalez: Created page with "

'''Additional Steps for Automated Testing on QEMU'''

In general, the steps are very similar to those for generic images for BSP. The main difference, however, is..."

2016-10-20T00:57:55Z

Created page with "<h2>'''Additional Steps for Automated Testing on QEMU'''</h2> In general, the steps are very similar to those for generic images for BSP. The main difference, however, is..."

New page

<h2>'''Additional Steps for Automated Testing on QEMU'''</h2>


In general, the steps are very similar to those for generic images for BSP. The main difference, however, is that two poky repositories are needed, one for running QEMU with the downloaded image, and another for executing testimage. This is required as only one bitbake instance is allowed to be running per repository at a time.


Also, additional bitbake commands are required to construct the QEMU native image and its helper binaries.


 


Using qemux86 as an example, the steps are:


<h3>Setup the repository for executing QEMU</h3>


1. Download the core-image-sato-sdk-qemux86 image from autobuilder (link available in the point release mail).



2. Clone a clean version of poky and make checkout on the poky commit from the mail (in command line):


a) Clone a copy of a clean version of poky designing it for running QEMU ('poky-run' in this example, but naming is optional):

<pre>$ git clone git://git.yoctoproject.org/poky poky-run</pre>

b) In the poky directory, checkout the desired commit:

<pre>$ cd ~/poky-run</pre>
<pre>$ git checkout <commit-id></pre>


3. Source the environment, from poky directory:

<pre>$ source oe-init-build-env</pre>


4. Edit local.conf. PATH: ~/poky-run/build/conf, at the end of the file adding:

<pre>Add the required machine, for example MACHINE ?= "qemux86"</pre>


5. In ~/poky-run/build directory, in command line, type the following commands:

<pre>
$ bitbake qemu-native
$ bitbake qemu-helper-native
</pre>

NOTE: After finishing the tasks, copy the image bin, ext4 and qemuboot.conf files from autobuilder at the following path:
"~/poky-run/build/tmp/deploy/images/qemux86/" (if "tmp/deploy/images/qemux86" does not exist, create new directories with this path)



6. In ~/poky-run/build directory start the QEMU emulator:

<pre>runqemu qemux86</pre>


7. Obtain the virtual machine IP Address by opening a terminal inside it and executing ifconfig.


<h3>Setup the repository for executing testimage</h3>


1. Download the core-image-sato-sdk-qemux86 image from autobuilder, if required (this is the same step than for setting up the repository for executing QEMU).



2. Clone a clean version of poky and make checkout on the poky commit from the mail (in command line):


a) Clone a copy of a clean version of poky designing it for executing testimage ('poky-test' in this example, but naming is optional):

<pre>$ git clone git://git.yoctoproject.org/poky poky-test</pre>

b) In the poky directory, checkout the desired commit:

<pre>$ cd ~/poky-test</pre>
<pre>$ git checkout <commit-id></pre>


3. Source the environment, from poky directory:

<pre>$ source oe-init-build-env</pre>


4. Edit local.conf. PATH: ~/poky-test/build/conf, at the end of the file adding:

<pre>
INHERIT += "testimage"
TEST_TARGET = "simpleremote"
TEST_SERVER_IP = "HOST ip" --> IP of the machine being used to launch tests
TEST_TARGET_IP = "DUT ip" --> IP of the device under test
TEST_SUITES = " auto"

Remember to add the required machine, for example MACHINE ?= "qemux86"
</pre>


5. In the repository designed to execute testimage, edit bblayers.conf PATH: ~/poky-test/build/conf

<ul><li>in " BBLAYERS ?= " \ " section add "meta-selftest" respecting the pattern from above</li></ul>


6. In ~/poky-test/build directory, in command line, type the following commands:

<pre>
$ bitbake rpm psplash
$ bitbake package-index
</pre>

NOTE: After finishing the tasks, copy the image manifest (core-image-sato-sdk-qemux86.manifest) from autobuilder at the following path:
"~/poky-test/build/tmp/deploy/images/qemux86/" (if "tmp/deploy/images/qemux86" does not exist, create new directories with this path).



7. In ~/poky-test/build directory, start the testimage execution by typing the following command:

<pre>$ bitbake core-image-sato-sdk -c testimage</pre>

If you face issues with the keys from your host, use this command: $ ssh-keygen -f /home/user/.ssh/known_hosts -R targetip
Then add the key to the host again ssh , SSH TARGETNAME@IPTARGET
After a while the testing will be finished.

Steps for Automated Testing on QEMU - Revision history

Jose G Perez Carranza at 16:03, 8 March 2017

Jair Gonzalez at 21:44, 27 October 2016

Jair Gonzalez: Editing page title to better reflect its content.

Jair Gonzalez: Jair Gonzalez moved page Additional Steps for Automated Testing on QEMU to Steps for Automated Testing on QEMU: Changing the title of the page to better reflect its content, as not only additional steps for automated testing are mentioned in it...

Jair Gonzalez: Created page with "

'''Additional Steps for Automated Testing on QEMU'''