All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Yeoh, Ee Peng" <ee.peng.yeoh@intel.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Cc: "Eggleton, Paul" <paul.eggleton@intel.com>
Subject: Re: [PATCH] oe-selftest: qemutest: add tests for qemu boot and shutdown
Date: Thu, 5 Apr 2018 12:55:31 +0300	[thread overview]
Message-ID: <c10d7df8-2f5e-b288-afc8-499f47f76724@linux.intel.com> (raw)
In-Reply-To: <9DDD2658D1FE414E99172D2DB1E4D04335E0006E@PGSMSX109.gar.corp.intel.com>

On 04/05/2018 11:09 AM, Yeoh, Ee Peng wrote:
> I had developed this selftest testcase to test qemu can boot nfs &
> ext4 and finally shutdown for various qemu architecture.
> 
> Initially, I was thinking to develop this automated test as part of
> testimage but as this test involve shutting down qemu, testimage
> testcases executed after this will face lost connection to qemu.
> Furthermore, when I tried to add this test to selftest runqemu.py, I
> realized runqemu was dedicated for MACHINE=qemux86-64 and it was
> testing various live image (iso and hddimg) but live image was not
> supported by other qemu architecture. Therefore, this test was
> developed as independent selftest testcase.
> 
> Please let me know your inputs and feedback.
It's totally okay to have several test classes in a single .py file (see 
for example signing.py). I think this should go to runqemu.py, as 
otherwise there would be two different files doing roughly same thing 
and named very similarly (runqemu and qemutest?), which is confusing.

You can add comments to both classes to explain what they do and why, 
and how they are different. (generally, be generous with comments every 
time there is possibility for confusion, or the code does unusual things 
etc.)

Alex


  reply	other threads:[~2018-04-05 10:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05  0:35 [PATCH] oe-selftest: qemutest: add tests for qemu boot and shutdown Yeoh Ee Peng
2018-04-05  8:09 ` Yeoh, Ee Peng
2018-04-05  9:55   ` Alexander Kanavin [this message]
2018-04-06  0:46     ` 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=c10d7df8-2f5e-b288-afc8-499f47f76724@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=ee.peng.yeoh@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@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 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.