From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: jose.perez.carranza@linux.intel.com,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] runtime/dnf: Add new dnf test cases
Date: Wed, 10 May 2017 22:52:14 +0300 [thread overview]
Message-ID: <bd532acb-3dda-ac74-37d8-892fc797a407@linux.intel.com> (raw)
In-Reply-To: <20170510193809.2356-1-jose.perez.carranza@linux.intel.com>
On 05/10/2017 10:38 PM, jose.perez.carranza@linux.intel.com wrote:
> + def test_dnf_installroot(self):
> + rootpath = '/home/root/chroot/test'
> + self.dnf_with_repo('install --installroot=%s --allowerasing -v -y busybox run-postinsts' % rootpath)
> + status, output = self.target.run('test -e %s/var/cache/dnf' % rootpath, 1500)
> + self.assertEqual(0, status, output)
You could also check there that the files from installed packages are
indeed there (e.g. /home/root/chroot/test/bin/sh and such). Just in case. :)
> + def test_dnf_exclude(self):
> + excludepkg = 'run-postinsts-dev'
> + self.dnf_with_repo('remove -y run-postinsts')
> + self.dnf_with_repo('install -y --exclude=%s run-postinsts' % excludepkg)
> + self.dnf('list %s' % excludepkg, 1)
How does this test work? I do not understand. First run-postinsts is
removed, then it is installed again with --exclude=run-postinsts-dev,
then we check that run-postinst-dev is not installed. Would it have been
installed without the --exclude option? Why, if we're only asking for
run-postinsts?
If it would, should you test that it does indeed happen, to make sure
there is indeed a difference in the outcome when --exclude is present
and absent?
Alex
next prev parent reply other threads:[~2017-05-10 19:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 19:38 [PATCH] runtime/dnf: Add new dnf test cases jose.perez.carranza
2017-05-10 19:52 ` Alexander Kanavin [this message]
2017-05-11 17:33 ` [PATCH v2] " jose.perez.carranza
2017-05-11 18:56 ` Alexander Kanavin
2017-05-11 19:21 ` Jose Perez Carranza
2017-05-15 13:50 ` [PATCH v3] " jose.perez.carranza
2017-06-07 10:21 ` Burton, Ross
2017-06-07 17:31 ` Jose Perez Carranza
2017-06-08 11:31 ` Alexander Kanavin
2017-06-08 12:49 ` Jose Perez Carranza
2017-06-08 12:49 ` Alexander Kanavin
2017-06-08 13:11 ` Jose Perez Carranza
2017-06-08 16:35 ` Alexander Kanavin
2017-06-09 9:22 ` Alexander Kanavin
2017-06-09 12:54 ` Jose Perez Carranza
2017-06-13 19:56 ` [PATCH v4] " jose.perez.carranza
2017-06-14 12:00 ` Alexander Kanavin
2017-06-14 12:32 ` Jose Perez Carranza
2017-11-30 16:23 ` [PATCH v5] " jose.perez.carranza
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=bd532acb-3dda-ac74-37d8-892fc797a407@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=jose.perez.carranza@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