From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: yocto@yoctoproject.org
Subject: RFC: automated runtime testing on real hardware
Date: Tue, 13 Aug 2013 12:00:08 +0100 [thread overview]
Message-ID: <2594690.j9UepmO1kG@helios> (raw)
Hi all,
As part of the feature development work for 1.5, we've recently added the
ability to easily define runtime tests written in python, replacing the old
shell-based imagetest.bbclass. However, for 1.5 this is limited to running the
tests within a QEMU environment; the obvious and desirable next step is to be
able to have these run on real hardware. Clearly this presents some
challenges, such as how to manage access to the hardware if you have multiple
builders potentially wanting to use the same board at around the same time.
Automated testing on real hardware is something that a lot of us do already,
but the likelihood is that we've all been coming up with our own solutions for
this, so it would be really great if we could have a single working solution
to cover the generally applicable use cases. As a start though it would be
interesting to hear from people who have existing test setups or who are
generally interested in this area. I'd like to hear feedback on the following:
* What hardware setup do you use for automated testing?
* Do you use any software to manage the hardware? Does this include any
existing open source tools?
* What would you like to see in a common framework to enable this kind of
testing?
For reference, some discussion on this started in another thread [1], but I'd
like to throw this out to a more general audience.
Thanks,
Paul
[1] https://lists.yoctoproject.org/pipermail/yocto/2013-August/017687.html
--
Paul Eggleton
Intel Open Source Technology Centre
next reply other threads:[~2013-08-13 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 11:00 Paul Eggleton [this message]
2013-08-24 3:52 ` RFC: automated runtime testing on real hardware Darren Hart
2013-08-27 11:11 ` Paul Eggleton
2013-08-27 15:20 ` Darren Hart
-- strict thread matches above, loose matches on Subject: below --
2013-08-15 22:13 George Harris
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=2594690.j9UepmO1kG@helios \
--to=paul.eggleton@linux.intel.com \
--cc=yocto@yoctoproject.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.