From: Stefan Stanacar <stefanx.stanacar@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] testimage/oeqa: Add ability to export tests to decouple them from the build system
Date: Mon, 3 Feb 2014 21:22:28 +0200 [thread overview]
Message-ID: <cover.1391454072.git.stefanx.stanacar@intel.com> (raw)
Hello,
These patches add the ability to export and run tests outside of the build.
As tests used to query values from the data storage this exports parts of d
and makes them avaiable in a json file, so tests don't need to change to
make them exportable. Tests exported are the ones defined in TEST_SUITES regardless
of layer.
Starting the target (in the default case qemu) is still handled by the build system, as before,
so keep that in mind.
Simplest way to test this is with a qemu image that you manually start.
For an already build image use this in local.conf:
TEST_EXPORT_ONLY = "1"
TEST_TARGET = "simpleremote"
TEST_TARGET_IP = "192.168.7.2"
TEST_SERVER_IP = "192.168.7.1"
Export the tests: bitbake core-image-sato -c testimage
Then: runqemu core-image-sato
And: cd tmp/testimage/core-image-sato && ./runexported.py testdata.json
In the default case (TEST_EXPORT_ONLY = "0") nothing really changes
so no tests should start failing because of this.
Cheers,
Stefan
The following changes since commit 76f52a81f600fe7dfee0987db361e973b9ab71f8:
insane: Fix python function whitespace changes (2014-02-03 16:16:30 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib stefans/export
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=stefans/export
Stefan Stanacar (3):
testimage: add ability to export tests
lib/oeqa: add module for running tests outside of the build system
oeqa/utils: targetbuild: don't use bb.fetch anymore
meta/classes/testimage.bbclass | 107 ++++++++++++++++++++++++----
meta/lib/oeqa/oetest.py | 17 ++---
meta/lib/oeqa/runexported.py | 140 +++++++++++++++++++++++++++++++++++++
meta/lib/oeqa/utils/targetbuild.py | 27 +++----
4 files changed, 246 insertions(+), 45 deletions(-)
create mode 100755 meta/lib/oeqa/runexported.py
--
1.8.5.3
next reply other threads:[~2014-02-03 19:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 19:22 Stefan Stanacar [this message]
2014-02-03 19:22 ` [PATCH 1/3] testimage: add ability to export tests Stefan Stanacar
2014-02-03 19:22 ` [PATCH 2/3] lib/oeqa: add module for running tests outside of the build system Stefan Stanacar
2014-02-03 19:22 ` [PATCH 3/3] oeqa/utils: targetbuild: don't use bb.fetch anymore Stefan Stanacar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1391454072.git.stefanx.stanacar@intel.com \
--to=stefanx.stanacar@intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox