From: Yuan Sun <Yuan.Sun2@windriver.com>
To: "Damian, Alexandru" <alexandru.damian@intel.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
"Zhao, Yi" <Yi.Zhao@windriver.com>,
"Zhao, Zhenfeng" <zhenfeng.zhao@windriver.com>,
"toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: Re: Reference browser for testing purposes
Date: Thu, 20 Mar 2014 11:38:50 +0800 [thread overview]
Message-ID: <532A62CA.6060403@windriver.com> (raw)
In-Reply-To: <CAJ2CSBtFxstV=+fD7Jz9iDotUO5Fj2n08i8PfAWxJ378u00kEA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2971 bytes --]
Hi all,
From a tester's views, I choose Ubuntu 12.04 as a test host. Firefox 11.0
is a default web browser in Ubuntu 12.04. Ubuntu 12.04 is a long-term support
release. It has continuous hardware support improvements as well as guaranteed
security and support updates until April 2017. However, Ubuntu 13.10(the latest
version) will be supported for *ONLY* 9 months. So I think that Ubuntu 12.04 is
a popular version and so many users would use it. Choose it as a test
environment would covers a great percentage of users.
Maybe we can create a recommendation list of web-browser for customers so
that it can lead to good user experience.
Thanks.
Yuan
On 14-03-20 02:14 AM, Damian, Alexandru wrote:
>
> Our goal is not "decent" but complete HTML5 compatibility.
>
> The target is that our HTML output is to be validated by HTML5 validators with
> no errors shown. We already selected the industry-standard HTML5 validators to
> verify this.
> Specifically, we are using in development http://validator.w3.org/ through a
> browser extension. This MUST be automated at a certain point.
>
> What I'm trying to avoid here is coding specifically for a target browser or
> platform. I suggest to not restrict testing to a certain
> browser/platform/version, but use what ever the tester uses in real life.
> In case of presentation bugs are discovered, first we have to rule out an
> issue with the browser of choice by testing visual reproducibility with
> another browser on the same page and verifying browser's HTML5 compatibility.
>
> For visual reference, widgets in the page change across different platforms
> and browsers. Do we have test cases for the appearance ?
>
> The test cases should not be dependent or executed with a specified
> platform/browser version.
>
> Cheers,
> Alex
>
>
>
> On Wed, Mar 19, 2014 at 4:23 PM, Barros Pena, Belen
> <belen.barros.pena@intel.com <mailto:belen.barros.pena@intel.com>> wrote:
>
> We should probably have raised this question earlier and had a plan in
> place, but hey, better late ... The question is: which browsers should we
> be using as a reference for QA purposes? Our guideline here is decent
> HTML5 compatibility, but we never qualified what 'decent' means.
>
> The other reference we could use is traffic to the Yocto Project website.
> Visits are mainly coming from Chrome 32 and 33 on Windows, and Firefox 26
> and 27 on Linux. I can put together more detailed numbers if anybody wants
> to see them.
>
> Those might be a bit too cutting edge, but could guide our decision
> somehow. QA is currently testing with Firefox 11: that is probably too
> old.
>
> In light of the above, any suggestions about which browsers we should use
> for testing?
>
> Thanks!
>
> Belén
>
>
>
>
> --
> Alex Damian
> Yocto Project
> SSG / OTC
[-- Attachment #2: Type: text/html, Size: 6021 bytes --]
next prev parent reply other threads:[~2014-03-20 3:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 16:23 Reference browser for testing purposes Barros Pena, Belen
2014-03-19 17:21 ` Georgescu, Alexandru C
2014-03-19 18:14 ` Damian, Alexandru
2014-03-20 3:38 ` Yuan Sun [this message]
2014-03-20 11:09 ` Barros Pena, Belen
-- strict thread matches above, loose matches on Subject: below --
2014-03-28 12:12 Barros Pena, Belen
2014-03-28 18:41 ` Paul Eggleton
2014-03-28 18:56 ` Gary Thomas
2014-03-31 8:28 ` Barros Pena, Belen
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=532A62CA.6060403@windriver.com \
--to=yuan.sun2@windriver.com \
--cc=Yi.Zhao@windriver.com \
--cc=alexandru.damian@intel.com \
--cc=paul.eggleton@linux.intel.com \
--cc=toaster@yoctoproject.org \
--cc=zhenfeng.zhao@windriver.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.