Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] Support tests in other layers
Date: Sun, 25 Aug 2013 01:46:54 +0100	[thread overview]
Message-ID: <cover.1377390888.git.paul.eggleton@linux.intel.com> (raw)

Completion of an earlier work-in-progress change by Stefan. I had
earlier suggested using a special "tests/runtime" directory in other
layers that wish to add their own tests, but when I looked into it I
figured it was actually a lot simpler if we kept the same structure as
the tests in OE-Core i.e. lib/oeqa/runtime, since sys.path is already
extended in base.bbclass to make that work for all layers; we just
needed to tweak __init__.py in the oeqa/runtime directory to enable
unittest to import units from other layers in that same directory.


The following changes since commit e473e60d5572f36829068f6d3db9ce9ba9633d71:

  mkfontscale: This no longer needs a full libx11, xproto suffices (2013-08-22 18:29:50 +0100)

are available in the git repository at:

  git://git.openembedded.org/openembedded-core-contrib paule/testimage
  http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/testimage

Stefan Stanacar (1):
  classes/testimage: add support for finding tests in other layers

 meta/classes/testimage.bbclass    | 55 ++++++++++++++++++++++++++++++---------
 meta/lib/oeqa/runtime/__init__.py |  3 +++
 2 files changed, 46 insertions(+), 12 deletions(-)

-- 
1.8.1.2



             reply	other threads:[~2013-08-25  0:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-25  0:46 Paul Eggleton [this message]
2013-08-25  0:46 ` [PATCH 1/1] classes/testimage: add support for finding tests in other layers Paul Eggleton

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.1377390888.git.paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.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