Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Phil Blundell <pb@pbcl.net>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: RFC: Web browsing and HTML in OE-Core
Date: Fri, 23 Aug 2013 17:14:33 +0100	[thread overview]
Message-ID: <1377274473.6762.100.camel@ted> (raw)
In-Reply-To: <1377273397.5452.43.camel@phil-desktop.brightsign>

On Fri, 2013-08-23 at 16:56 +0100, Phil Blundell wrote:
> On Fri, 2013-08-23 at 12:17 +0100, Richard Purdie wrote:
> > I think ultimately we need both, a real world user of webkit and also a
> > webkit-ptest type package too. They both let us test different things,
> > one probably more quickly than the other, with the other being more
> > complete.
> 
> Well, logically that would mean that we'd need a real-world user of
> webkit for every port (or at least, for the three ports that are
> currently supportable within oe-core).  It's not obvious that this would
> scale very well.
> 
> What are the things that you think would be tested better with midori
> than with the standalone launcher and test wrappers?

What does the standalone launcher give you?

What I'm thinking is that having a browser interface QA can click on
from the desktop and enter say 5 urls into is fast yet tests a
significant amount of the system, much like booting X on a system
doesn't test everything but it does test a fair amount of simple things
like whether the binaries work.

Cheers,

Richard




  reply	other threads:[~2013-08-23 16:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-22 14:04 RFC: Web browsing and HTML in OE-Core Richard Purdie
2013-08-22 14:18 ` Phil Blundell
2013-08-23 11:17   ` Richard Purdie
2013-08-23 15:56     ` Phil Blundell
2013-08-23 16:14       ` Richard Purdie [this message]
2013-08-23 17:03         ` Phil Blundell
2013-08-22 14:24 ` Samuel Stirtzel
2013-08-23 11:16   ` Richard Purdie
2013-08-22 17:24 ` Otavio Salvador

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=1377274473.6762.100.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pb@pbcl.net \
    /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