Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Tim Orling <timothy.t.orling@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/7] Enable easier ptest of perl modules
Date: Sun,  4 Mar 2018 04:41:48 -0800	[thread overview]
Message-ID: <cover.1520166347.git.timothy.t.orling@linux.intel.com> (raw)

We need run-time testing in order to ensure recipe quality and
automating this is easiest with ptest.

* Add a new ptest-perl.bbclass which:
  - copies tests that almost all perl modules will have in t/ to PTEST_PATH
  - uses a common run-ptest script (from meta-perl recipes)
  - runs install_ptest_perl task after install_ptest
    = checks that run-ptest is not already present

For many perl recipes, using this class will be as simple as:
"inherit ptest-perl"

To run the tests, follow the ptest instructions in the dev-manual [1] and
then run "ptest-runner libfoo-perl" on target.

Tested on qemux86 with all oe-core lib*-perl recipes with no failures.

[1] http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#testing-packages-with-ptest

The following changes since commit 8e4ece7bf0b09275a34ce8e7cc3e1e54a366c361:

  glibc: Enable static PIE support when security_flags are enabled (2018-03-01 22:18:00 +0000)

are available in the Git repository at:

  git://git.openembedded.org/openembedded-core-contrib timo/ptest-perl
  http://cgit.openembedded.org//log/?h=timo/ptest-perl

Tim Orling (7):
  meta/classes: add ptest-perl.bbclass
  libtest-needs-perl: add 0.002005
  liberror-perl: inherit ptest-perl
  liburi-perl: inherit ptest-perl
  libxml-parser-perl: inherit ptest-perl
  libxml-perl: inherit ptest-perl
  libxml-simple-perl: inherit ptest-perl

 meta/classes/ptest-perl.bbclass                    | 30 ++++++++++++++++++++++
 meta/files/ptest-perl/run-ptest                    | 16 ++++++++++++
 .../recipes-devtools/perl/liberror-perl_0.17025.bb |  7 ++++-
 .../perl/libtest-needs-perl_0.002005.bb            | 29 +++++++++++++++++++++
 meta/recipes-devtools/perl/liburi-perl_1.73.bb     | 10 +++++++-
 .../perl/libxml-parser-perl_2.44.bb                | 11 +++++++-
 meta/recipes-devtools/perl/libxml-perl_0.08.bb     |  2 +-
 .../perl/libxml-simple-perl_2.24.bb                |  2 +-
 8 files changed, 102 insertions(+), 5 deletions(-)
 create mode 100644 meta/classes/ptest-perl.bbclass
 create mode 100644 meta/files/ptest-perl/run-ptest
 create mode 100644 meta/recipes-devtools/perl/libtest-needs-perl_0.002005.bb

-- 
2.14.3



             reply	other threads:[~2018-03-04 12:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-04 12:41 Tim Orling [this message]
2018-03-04 12:41 ` [PATCH 1/7] meta/classes: add ptest-perl.bbclass Tim Orling
2018-03-04 12:41 ` [PATCH 2/7] libtest-needs-perl: add 0.002005 Tim Orling
2018-03-04 17:24   ` Richard Purdie
2018-03-04 22:55     ` Tim Orling
2018-03-04 12:41 ` [PATCH 3/7] liberror-perl: inherit ptest-perl Tim Orling
2018-03-04 12:41 ` [PATCH 4/7] liburi-perl: " Tim Orling
2018-03-04 12:41 ` [PATCH 5/7] libxml-parser-perl: " Tim Orling
2018-03-04 12:41 ` [PATCH 6/7] libxml-perl: " Tim Orling
2018-03-04 12:41 ` [PATCH 7/7] libxml-simple-perl: " Tim Orling

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.1520166347.git.timothy.t.orling@linux.intel.com \
    --to=timothy.t.orling@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