- From: Abel Rionda <abel.rionda@fundacionctic.org>
- Date: Mon, 28 Jan 2008 18:15:26 +0100
- To: <public-mobileok-checker@w3.org>
Hello all,
We have committed the changes regarding these bugs.
As remainder, the changes mainly involve 2.4.3[1] and 2.4.4[2] points
of the mobileOKBasicTests.
There is a new test MAIN_DOCUMENT that groups HTTP_RESPONSE_* and
META_HTTP_EQUIV-1
(META_HTTP_EQUIV-2 is not implemented yet) regarding main resource under
test.
Additionally every HTTP_RESPONSE related to included or external
resources are reported in the suitable
test. For example a test result for a LINK_TARGET_FORMAT test could be:
<test name="LINK_TARGET_FORMAT" outcome="PASS">
<result name="HTTP_RESPONSE-12" outcome="WARN">
<info>WARN: The HTTP status indicates that authentication is
required (e.g. status code 401) and the response relates to a request
for a linked resource </info>
</result>
<result name="LINK_TARGET_FORMAT-3" outcome="WARN">
<info>WARN: The internal reference test has no matching
target</info>
</result>
</test>
Although this solution could be discussed (as Dom mentioned it), we
commit the changes in order to have a version (for Beta) which
implements
HTTP response tests.
Dom pointed out the following:
>I think it shouldn't send the LINK_TARGET_FORMAT warning in addition to
>the HTTP_RESPONSE one - i.e. I think the tests that depend on analyzing
>the content of an HTTP requests shouldn't be run on the retrieved
>resource if that retrieval triggered an HTTP error.
But we think that HTTP tests are transversal to all tests that are
checked on
resources (included or external), so we think that they should be added
in the
corresponding test result.
We have made some unit tests for MAIN_DOCUMENT and LINK_TARGET_FORMAT
tests.
[1] http://www.w3.org/TR/mobileOK-basic10-tests/#http_response
[2] http://www.w3.org/TR/mobileOK-basic10-tests/#meta_http_equiv
Miguel and Abel
Received on Monday, 28 January 2008 17:15:38 UTC