sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

dev-manual: Updates to "Performing Automated Runtime Testing" 

Fixes [YOCTO #5554]

I worked with Stefan here to update the section on running tests.
We are good now with it all.

(From yocto-docs rev: 806a89f1ddd3efc39d15d3f7e1a01e8fd69af7c1)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2014-04-18 09:08:55 -07:00 committed by Richard Purdie
parent ac054daa36
commit 2648f5d972
1 changed files with 69 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

74
documentation/dev-manual/dev-manual-common-tasks.xml
View File

@ -5801,13 +5801,31 @@
(or something similar) is installed.
Also, your hardware under test must be in a
DHCP-enabled network that gives it the same IP
address for each reboot.
address for each reboot.</para>
<para>If you choose "GummibootTarget", there are
additional requirements and considerations.
See the
"<link linkend='selecting-gummiboottarget'>Selecting GummibootTarget</link>"
section, which follows, for more information.
</para></listitem>
</itemizedlist>
</para>
</section>
<section id='selecting-gummiboottarget'>
<title>Selecting GummibootTarget</title>
<para>
If you set <filename>TEST_TARGET</filename> to
If you did not set <filename>TEST_TARGET</filename> to
"GummibootTarget", then you do not need any information
in this section.
You can skip down to the
"<link linkend='qemu-image-running-tests'>Running Tests</link>"
section.
</para>
<para>
If you did set <filename>TEST_TARGET</filename> to
"GummibootTarget", you also need to perform a one-time
setup of your master image by doing the following:
<orderedlist>
@ -5821,11 +5839,57 @@
<listitem><para><emphasis>Build the master image:</emphasis>
Build the <filename>core-image-testmaster</filename>
image.
The <filename>core-image-testmaster</filename>
recipe is provided as an example for a
"master" image and you can customize the image
recipe as you would any other recipe.
</para>
<para>Here are the image recipe requirements:
<itemizedlist>
<listitem><para>Inherits
<filename>core-image</filename>
so that kernel modules are installed.
</para></listitem>
<listitem><para>Installs normal linux utilities
not busybox ones (e.g.
<filename>bash</filename>,
<filename>coreutils</filename>,
<filename>tar</filename>,
<filename>gzip</filename>, and
<filename>kmod</filename>).
</para></listitem>
<listitem><para>Uses a custom
initramfs image with a custom installer.
A normal image that you can install usually
creates a single rootfs partition.
This image uses another installer that
creates a specific partition layout.
Not all Board Support Packages (BSPs)
can use an installer.
For such cases, you need to manually create
the following partition layout on the
target:
<itemizedlist>
<listitem><para>First partition mounted
under <filename>/boot</filename>,
labeled "boot".
</para></listitem>
<listitem><para>The main rootfs
partition where this image gets
installed, which is mounted under
<filename>/</filename>.
</para></listitem>
<listitem><para>Another partition
labeled "testrootfs" where test
images get deployed.
</para></listitem>
</itemizedlist>
</para></listitem>
</itemizedlist>
</para></listitem>
<listitem><para><emphasis>Install image:</emphasis>
Install the image on the target system.
&lt;Need some clarification here from Stefan,
partition layout, etc.&gt;
Install the image that you just built on the target
system.
</para></listitem>
</orderedlist>
</para>