From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Yeoh Ee Peng <ee.peng.yeoh@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] oe-selftest: runqemu: add tests for qemu boot and shutdown
Date: Tue, 10 Apr 2018 10:41:02 +0100 [thread overview]
Message-ID: <1523353262.2942.143.camel@linuxfoundation.org> (raw)
In-Reply-To: <1523295825-118054-1-git-send-email-ee.peng.yeoh@intel.com>
On Mon, 2018-04-09 at 10:43 -0700, Yeoh Ee Peng wrote:
> QA team were testing qemu boot image and shutdown on each
> qemu architecture manually. Add automated test to test qemu boot on
> ext4 and nfs, finally check that it can shutdown properly.
>
> Original runqemu tests was dedicated for MACHINE=qemux86-64 and
> it was testing various live image (iso and hddimg) will be able
> to boot while live image was not supported on all qemu architecture.
>
> The new tests were designed as a separate class as this tests
> focus on testing qemu boot and shutdown on each qemu architecture.
> Furthermore, this tests focus on testing qemu could shutdown
> as expected.
>
> Signed-off-by: Yeoh Ee Peng <ee.peng.yeoh@intel.com>
I do have one other question about this. There are various other tests
which boot qemu images. Would we be able to assume that because those
tests work, the start/stop of qemu is working? Or is there a unique
element we need to test specifically here?
Cheers,
Richard
next prev parent reply other threads:[~2018-04-10 9:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 17:43 [PATCH] oe-selftest: runqemu: add tests for qemu boot and shutdown Yeoh Ee Peng
2018-04-10 1:01 ` Yeoh, Ee Peng
2018-04-10 7:00 ` Anuj Mittal
2018-04-10 7:24 ` Yeoh, Ee Peng
2018-04-10 7:29 ` Alexander Kanavin
2018-04-10 7:39 ` Yeoh, Ee Peng
2018-04-10 9:41 ` Richard Purdie [this message]
2018-04-10 10:01 ` Yeoh, Ee Peng
-- strict thread matches above, loose matches on Subject: below --
2018-04-10 1:28 Yeoh Ee Peng
2018-04-20 7:15 ` Richard Purdie
2018-04-20 8:27 ` Yeoh, Ee Peng
2018-04-09 3:32 Yeoh Ee Peng
2018-04-09 12:34 ` Alexander Kanavin
2018-04-10 0:57 ` Yeoh, Ee Peng
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=1523353262.2942.143.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=ee.peng.yeoh@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