All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Robert Berger <gmane@reliableembeddedsystems.com>
Cc: yocto@yoctoproject.org
Subject: Re: [Announcement] Yocto Project 1.5 Milestone 3 now available.
Date: Sat, 10 Aug 2013 11:02:29 +0100	[thread overview]
Message-ID: <3217805.kYDiUIXKQu@helios> (raw)
In-Reply-To: <5205E9D6.6020408@reliableembeddedsystems.com>

Hi Robert,

On Saturday 10 August 2013 10:20:54 Robert Berger wrote:
> On 08/10/2013 03:22 AM, Flanagan, Elizabeth wrote:
> > * Infrastructure for automated QA testing. More testcases will be
> > automated in the next milestone release.
> 
> Are we talking about test automation using autobuilder here?
> As far as I can see runtime testing of images using QEMU is
> planned/already used.

The new framework replaces the old, is written in python and makes writing 
tests much easier. As a result we are going through a process of adding many 
more runtime tests than we had previously.

> What I'm after is runtime testing on real hardware. Assuming an
> infrastructure where you can remotely turn on/off the power of the board
> and where you have access e.g. via a conserver to the serial port I
> guess this should be possible as well.
> 
> I'm wondering why this seems to be limited to QEMU, am I missing something?

We do definitely want automated testing on real hardware; it's just that that 
it presents a number of problems that need solving:

 * How do you deploy the image/kernel/bootloader onto the board in an 
automated manner? To different kinds of boards?
 * How do you manage access to the boards when you have multiple autobuilders 
potentially wanting to make use of them at around the same time?

We'll be working through these but the likelihood is that we won't have this 
part of it for 1.5. Once we do though, connecting the currently QEMU-based 
testing framework to it should be trivial.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2013-08-10 10:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-10  0:22 [Announcement] Yocto Project 1.5 Milestone 3 now available Flanagan, Elizabeth
2013-08-10  7:20 ` Robert Berger
2013-08-10 10:02   ` Paul Eggleton [this message]
2013-08-11  7:03     ` Robert Berger
2013-08-12  9:44       ` Paul Eggleton
2013-08-13  8:21         ` Robert Berger
2013-08-12  9:11     ` Björn Stenberg
2013-08-12  9:28       ` Paul Eggleton
2013-08-12 11:30         ` Björn Stenberg
2013-08-13  8:15           ` Robert Berger
2013-08-13 10:33             ` Björn Stenberg
2013-08-13  8:18         ` Robert Berger

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=3217805.kYDiUIXKQu@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=gmane@reliableembeddedsystems.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.