From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
Julien Stephan <jstephan@baylibre.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [RESEND 1/1] libexif: add ptest support
Date: Mon, 07 Aug 2023 14:39:57 +0100 [thread overview]
Message-ID: <9a501820b6be02e45069bbcd0e804f1f63017116.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj8=HDJrMyF21pGbNRD3L6G-_cVdMMQ=_CU0ev_GgAzjcA@mail.gmail.com>
On Thu, 2023-08-03 at 15:50 +0200, Alexander Kanavin wrote:
> What do the tests actually do? If they test libexif functionality in
> isolation, is there a need to run them, if upstream does this anyway?
> ptests are primarily meant for integration testing, e.g. exposing
> issues that arise in a complete customized system.
I've noticed a few replies about this and I do disagree slightly.
ptests are useful to ensure that the recipes in question actually work.
I'm sure most upstreams do test things but probably not on weirder
targets like mips/powerpc or with musl.
For something like libexif, if the ptests test the library functions
properly, returning the right test data for a sample for example, then
that is a useful for us.
Cheers,
Richard
prev parent reply other threads:[~2023-08-07 13:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 13:29 [RESEND 0/1] Add ptest support for libexif Julien Stephan
2023-08-03 13:29 ` [RESEND 1/1] libexif: add ptest support Julien Stephan
2023-08-03 13:50 ` [OE-core] " Alexander Kanavin
2023-08-07 13:33 ` Julien Stephan
2023-08-07 13:39 ` Richard Purdie [this message]
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=9a501820b6be02e45069bbcd0e804f1f63017116.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=jstephan@baylibre.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