diff options
| author |   Scott Rifenbark <srifenbark@gmail.com> | 2016-11-03 14:10:18 -0700 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-11-16 10:37:58 +0000 |
| commit | 0a2251780110305a0f986db3955af7db543a30c9 (patch) | |
| tree | 079f961f899f24e6770bcae33cfc30e3e26e1c5e /documentation/dev-manual/dev-manual-common-tasks.xml | |
| parent | 38366d30fc7f92c4f502cbf10f5af5bc902e0d6e (diff) | |
| download | openembedded-core-contrib-0a2251780110305a0f986db3955af7db543a30c9.tar.gz | |
dev-manual: Updated "Exporting Tests" section
Fixed [YOCTO #10588]
This section was confusing due to the fact that it used an actual
set of IP addresses and image name where they should be clearly
called out as examples. Fixed it.
(From yocto-docs rev: 006a25fad282b03aacd59eb8dc1a44cad2c19fc4)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual/dev-manual-common-tasks.xml')
| -rw-r--r-- | documentation/dev-manual/dev-manual-common-tasks.xml | 36 |
1 files changed, 28 insertions, 8 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 086d0bad99..95b8d2741d 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -9520,27 +9520,47 @@ <para> If your image is already built, make sure the following are set - in your <filename>local.conf</filename> file. - Be sure to provide the IP address you need: + in your <filename>local.conf</filename> file: <literallayout class='monospaced'> INHERIT +="testexport" - TEST_TARGET_IP = "192.168.7.2" - TEST_SERVER_IP = "192.168.7.1" + TEST_TARGET_IP = "<replaceable>IP-address-for-the-test-target</replaceable>" + TEST_SERVER_IP = "<replaceable>IP-address-for-the-test-server</replaceable>" </literallayout> - You can then export the tests with the following: + You can then export the tests with the following BitBake + command form: <literallayout class='monospaced'> - $ bitbake core-image-sato -c testexport + $ bitbake <replaceable>image</replaceable> -c testexport </literallayout> Exporting the tests places them in the <link linkend='build-directory'>Build Directory</link> in - <filename>tmp/testexport/core-image-sato</filename>, which - is controlled by the + <filename>tmp/testexport/</filename><replaceable>image</replaceable>, + which is controlled by the <filename>TEST_EXPORT_DIR</filename> variable. </para> <para> You can now run the tests outside of the build environment: <literallayout class='monospaced'> + $ cd tmp/testexport/<replaceable>image</replaceable> + $ ./runexported.py testdata.json + </literallayout> + </para> + + <para> + Here is a complete example that shows IP addresses and uses + the <filename>core-image-sato</filename> image: + <literallayout class='monospaced'> + INHERIT +="testexport" + TEST_TARGET_IP = "192.168.7.2" + TEST_SERVER_IP = "192.168.7.1" + </literallayout> + Use BitBake to export the tests: + <literallayout class='monospaced'> + $ bitbake core-image-sato -c testexport + </literallayout> + Run the tests outside of the build environment using the + following: + <literallayout class='monospaced'> $ cd tmp/testexport/core-image-sato $ ./runexported.py testdata.json </literallayout> |