From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 29C32E00480 for ; Wed, 19 Mar 2014 20:38:55 -0700 (PDT) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail.windriver.com (8.14.5/8.14.5) with ESMTP id s2K3cr1H014580 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 19 Mar 2014 20:38:54 -0700 (PDT) Received: from [128.224.159.139] (128.224.159.139) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server (TLS) id 14.3.169.1; Wed, 19 Mar 2014 20:38:53 -0700 Message-ID: <532A62CA.6060403@windriver.com> Date: Thu, 20 Mar 2014 11:38:50 +0800 From: Yuan Sun User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20120411 Thunderbird/11.0.1 MIME-Version: 1.0 To: "Damian, Alexandru" References: In-Reply-To: X-Originating-IP: [128.224.159.139] Cc: Paul Eggleton , "Zhao, Yi" , "Zhao, Zhenfeng" , "toaster@yoctoproject.org" Subject: Re: Reference browser for testing purposes X-BeenThere: toaster@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Web based interface for BitBake List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Mar 2014 03:39:04 -0000 Content-Type: multipart/alternative; boundary="------------070301040908070405040906" --------------070301040908070405040906 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit 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 > > 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 --------------070301040908070405040906 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: 8bit
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> 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 

--------------070301040908070405040906--