From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>,
Libertad Cruz <libertad.cruz@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V3] dpky.py: Adds testcases for dpkg package manager
Date: Fri, 29 Sep 2017 14:36:24 +0300 [thread overview]
Message-ID: <32c6875f-c796-5eb3-a720-5b9145837680@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LaLdMPpsypShHpxfdQRfBrxwgVSBUAFNS+mPKkohFVbDw@mail.gmail.com>
On 09/28/2017 04:28 PM, Burton, Ross wrote:
> On 27 September 2017 at 21:43, <libertad.cruz@intel.com
> <mailto:libertad.cruz@intel.com>> wrote:
>
> From: libertad <libertad.cruz@intel.com
> <mailto:libertad.cruz@intel.com>>
>
> Adds dpkg testcases for testing basic operation functionality for
> the dpkg packgage manager.Adds new assert function to verify
> expected results given by the dpkg package
>
>
> Basic functionality of a package manager is list packages, add packages,
> remove packages.
>
> Whereas the bulk of this this test verifies that four combinations of
> --help or --version work, which isn't actually testing anything beyond
> "is dpkg installed".
>
> Can we just remove all of them? I don't see the point in cluttering
> testopia and the source with test cases that don't actually test anything.
Useful dpkg testcases could be modeled on, for instance,
meta/lib/oeqa/runtime/cases/rpm.py.
Alex
next prev parent reply other threads:[~2017-09-29 11:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 20:43 [PATCH V3] dpky.py: Adds testcases for dpkg package manager libertad.cruz
2017-09-27 21:00 ` ✗ patchtest: failure for dpky.py: Adds testcases for dpkg package manager (rev4) Patchwork
2017-09-28 13:28 ` [PATCH V3] dpky.py: Adds testcases for dpkg package manager Burton, Ross
2017-09-29 11:36 ` Alexander Kanavin [this message]
2017-09-29 12:45 ` Alexander Kanavin
-- strict thread matches above, loose matches on Subject: below --
2017-09-27 20:04 libertad.cruz
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=32c6875f-c796-5eb3-a720-5b9145837680@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=libertad.cruz@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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