From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: Joshua Lock <joshua.lock@collabora.co.uk>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] wic/utils/partitionedfs.py: assemble .wic images as sparse files
Date: Thu, 17 Dec 2015 15:53:59 +0200 [thread overview]
Message-ID: <20151217135359.GA13025@linux.intel.com> (raw)
In-Reply-To: <5672B673.5030400@collabora.co.uk>
On Thu, Dec 17, 2015 at 01:19:47PM +0000, Joshua Lock wrote:
> Hi Ed,
>
> On 17/12/15 12:21, Ed Bartosh wrote:
> >Thank you for the patch! I like the change. It's a first step towards
> >supporting bmaptool, which is in my TODO list.
>
> No problem, I've been playing with bmaptool myself and that's what
> prompted the change.
>
> >Would you be willing to write or modify wic test case to test this?
>
> I'd be willing to do that, is there any documentation on the
> development of test cases?
You can find short info here:
https://wiki.yoctoproject.org/wiki/Oe-selftest
And here https://docs.python.org/2/library/unittest.html as oe-selftest
test cases are based on Python unittest.
> I see meta/lib/oeqa/selftest/wic.py has a bunch of functions with
> @testcase decorators but I'm not familiar with how this should all
> fit together.
You've spotted it right. All wic testcases are in that file.
You can run them this way: oe-selftest --run-tests wic
As Ross already pointed out you can omit @testcase decorator if you add
new test. QA team will add it later when they need it.
--
Regards,
Ed
next prev parent reply other threads:[~2015-12-17 14:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 16:33 [PATCH] wic/utils/partitionedfs.py: assemble .wic images as sparse files Joshua Lock
2015-12-17 12:21 ` Ed Bartosh
2015-12-17 13:19 ` Joshua Lock
2015-12-17 13:23 ` Burton, Ross
2015-12-17 13:53 ` Ed Bartosh [this message]
2015-12-17 16:09 ` [PATCH] oeqa/selftest/wic: add test case for sparse images Joshua Lock
2015-12-17 16:21 ` Burton, Ross
2015-12-17 16:52 ` Joshua Lock
2015-12-17 19:43 ` [[PATCH v2] " Joshua Lock
2015-12-30 9:53 ` Ed Bartosh
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=20151217135359.GA13025@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=joshua.lock@collabora.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.