W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2009

[widgets] Test Suite for Packaging and Configuration

From: Marcos Caceres <marcosc@opera.com>
Date: Fri, 7 Aug 2009 18:33:22 +0200
Message-ID: <b21a10670908070933y3bde5c50tb89be06e0a25329b@mail.gmail.com>
To: public-webapps <public-webapps@w3.org>, public-mwts@w3.org
I'm wondering, for the sake of testing, should we mandate the that in
order to run the test suite a user agent support the widgets A&E
specification? This would kinda sucks because we say in the spec that
a UA is not required to support of the Widgets A&E spec. However,
without the A&E spec, testing becomes a bit more difficult.

For example, consider the following testable assertion:

 "If this is not the first name element encountered by the user agent,
then the user agent must skip this element."

The test would be:

<!-- To pass, the second name element must be skipped by the user agent -->
<widget xmlns="http://www.w3.org/ns/widgets">

However, there is no way to visualize this test without using the
widgets A&E spec:
<!doctype html>
<body style="background-color:red">
  body = document.getElementsByTagName("body")[0];
  if(widget.name == "PASS"){
     body.innerHTML = "<h1>PASS </h1>";
     body.innerHTML = "<h1>FAIL</h1>";

Actually, there are some tests that cannot even be visualized with the
A&E spec... e.g., testing the <license> element, whose content is not
exposed via any attribute of the widget object. The only way for a UA
to verify if it passed, is to dump its internal representation of the
Configuration Defaults table.

Other things that suck about adding support for A&E is that tests are
no longer atomic. To actually get widget.name, about 100 other
preconditions need to have occurred.

Thoughts? Or have I answered my own question (don't test with the A&E
spec! :) )?

Kind regards,

Marcos Caceres
Received on Friday, 7 August 2009 16:34:29 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:18 UTC