dev-manual: Moved list of qemu-specific run information

Fixes [YOCTO #5554]

The list of items that described what happens when you run
tests is really specific to qemu.  Consequently, it is better
located in the section describing how to enable and get
set up for those tests.

(From yocto-docs rev: 1f0606f1c5c03c873a295819adcfb6fb51c196bd)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 35 insertions, 36 deletions

diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index dc61170fbf..b0cdc8342e 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -5712,6 +5712,41 @@
                             by <filename>runqemu</filename>.</para></listitem>
                     </itemizedlist>
                 </para>
+
+                <para>
+                    Once you start running the tests, the following happens:
+                    <itemizedlist>
+                        <listitem><para>A copy of the root filesystem is written
+                            to <filename>${WORKDIR}/testimage</filename>.
+                            </para></listitem>
+                        <listitem><para>The image is booted under QEMU using the
+                            standard <filename>runqemu</filename> script.
+                            </para></listitem>
+                        <listitem><para>A default timeout of 500 seconds occurs
+                            to allow for the boot process to reach the login prompt.
+                            You can change the timeout period by setting
+                            <ulink url='&YOCTO_DOCS_REF_URL;#var-TEST_QEMUBOOT_TIMEOUT'><filename>TEST_QEMUBOOT_TIMEOUT</filename></ulink>
+                            in the <filename>local.conf</filename> file.
+                            </para></listitem>
+                        <listitem><para>Once the boot process is reached and the
+                            login prompt appears, the tests run.
+                            The full boot log is written to
+                            <filename>${WORKDIR}/testimage/qemu_boot_log</filename>.
+                            </para></listitem>
+                        <listitem><para>Each test module loads in the order found
+                            in <filename>TEST_SUITES</filename>.
+                            You can find the full output of the commands run over
+                            SSH in
+                            <filename>${WORKDIR}/testimgage/ssh_target_log</filename>.
+                            </para></listitem>
+                        <listitem><para>If no failures occur, the task running the
+                            tests ends successfully.
+                            You can find the output from the
+                            <filename>unittest</filename> in the task log at
+                            <filename>${WORKDIR}/temp/log.do_testimage</filename>.
+                            </para></listitem>
+                    </itemizedlist>
+                </para>
             </section>
 
             <section id='hardware-image-enabling-tests'>
@@ -5796,42 +5831,6 @@
             </para>
 
             <para>
-                Regardless of how you run the tests, once they start, the
-                following happens:
-                <itemizedlist>
-                    <listitem><para>A copy of the root filesystem is written
-                        to <filename>${WORKDIR}/testimage</filename>.
-                        </para></listitem>
-                    <listitem><para>The image is booted under QEMU using the
-                        standard <filename>runqemu</filename> script.
-                        </para></listitem>
-                    <listitem><para>A default timeout of 500 seconds occurs
-                        to allow for the boot process to reach the login prompt.
-                        You can change the timeout period by setting
-                        <ulink url='&YOCTO_DOCS_REF_URL;#var-TEST_QEMUBOOT_TIMEOUT'><filename>TEST_QEMUBOOT_TIMEOUT</filename></ulink>
-                        in the <filename>local.conf</filename> file.
-                        </para></listitem>
-                    <listitem><para>Once the boot process is reached and the
-                        login prompt appears, the tests run.
-                        The full boot log is written to
-                        <filename>${WORKDIR}/testimage/qemu_boot_log</filename>.
-                        </para></listitem>
-                    <listitem><para>Each test module loads in the order found
-                        in <filename>TEST_SUITES</filename>.
-                        You can find the full output of the commands run over
-                        SSH in
-                        <filename>${WORKDIR}/testimgage/ssh_target_log</filename>.
-                        </para></listitem>
-                    <listitem><para>If no failures occur, the task running the
-                        tests ends successfully.
-                        You can find the output from the
-                        <filename>unittest</filename> in the task log at
-                        <filename>${WORKDIR}/temp/log.do_testimage</filename>.
-                        </para></listitem>
-                </itemizedlist>
-            </para>
-
-            <para>
                 All test files reside in
                 <filename>meta/lib/oeqa/runtime</filename> in the
                 <link linkend='source-directory'>Source Directory</link>.