PUBLIC MARKS with tag QA

The goal is simple : check that a set of web services are HTTP compliant.

The motivation for Jdrop came from my recent focus on mobile and subsequent launch of bookmarklets for mobile devices (Mobile Perf and Page Resources, followed by Docsource). I like using bookmarklets because they run on all mobile browsers that support JavaScript.

Jdrop provides a place to store JSON data in the cloud.

The initial application is for storing performance data gathered from mobile devices.

It's hard to analyze large amounts of information (HTTP waterfall charts, HTTP headers, document source, etc.) on a mobile device.

Jdrop lets you gather this data on the mobile device but analyze it remotely on a larger screen.

OperaWatir is a part of the Watir (pronounced water) family of free software Ruby libraries for automating web browsers. OperaWatir provides a querying engine and Ruby bindings for a backend Java library, OperaDriver, for driving the Opera web browser. It aims for full compliance with the watirspec specification.

Opera: Refer to the Q4 2009 GBS update for a discussion of the decision to move Opera to X-Grade. Worth noting here is that YUI specifically and Yahoo more broadly continue to support Opera — just as we continue to support X-Grade browsers in general. The GBS provides guidance for formulating QA testing matrices, and our recommendation as of Q1 2010 is that Opera be grouped in the X-Grade along with other high-quality, low-marketshare browsers. Opera is an excellent browser — we expect Opera users to have a good experience on Yahoo! sites and YUI-based sites, and we’ll continue to investigate bugs related to Opera as they are identified.

Web standards are complex software artifacts and like all software, they contain bugs. Sometimes the best way to find and fix compatibility bugs is to implement and deploy the standard on widely used browsers.

I can also easily deploy updates outside of our internal deploy cycle, which is nice.

The meta tags are intentional; they come from the RDFa syntax spec ([link]). We’re not exactly using the tags as intended by the Semantic Web community, but think that it’s the right balance between developer simplicity and standards.

Test for browser redirection handling WRT URI fragments, quick and dirty.

Bijan, a good test for the class of products is to read the spec with one class of products in mind.

* I'm an Authoring Tool Developer how do I implement html5,

* I'm a CMS developer how do I implement html5,

* I'm a automatic html translation engine how do I implement html5

Using http://www.w3.org/QA/Taxonomy.html can help to do this exercise.

etc. The html5 specification does a pretty good job at describing what some class of consumers should do. Not so much for other things.