- From: Charles McCathie Nevile <chaals@yandex-team.ru>
- Date: Fri, 04 Oct 2013 05:04:45 +0100
- To: "Webapps WG" <public-webapps@w3.org>, "Vincent Scheib" <scheib@google.com>
On Thu, 03 Oct 2013 22:50:21 +0100, Vincent Scheib <scheib@google.com>
wrote:
> Pointer lock is tricky to automate tests for. Consider some examples:
> - Upon lock, no pointer should be visible.
> - A user gesture is required to lock when not in fullscreen.
> - Transitioning to fullscreen and pointer lock then exiting fullscreen
> should maintain pointer lock. (User gesture required to enter fullscreen)
> - While locked, moving the mouse indefinitely in any direction must
> continue to provide non zero movementX/Y values.
>
> I'm considering starting some pointer lock tests with testharness.js. The
> only solution I see is to provide instructions in many tests
> for manual actions and observations.
>
> I appreciate any best practice suggestions, or pointers to other
> specifications with similar challenges. So far I see geolocation tests
> provide manual instructions.
Longdesc also has manual tests. The ones at
http://github.com/chaals/longdesc-tests are looking like they will be
accepted as actual tests. There is *1* automated test, which I haven't
tried to put it into testharness yet.
--
Charles McCathie Nevile - Consultant (web standards) CTO Office, Yandex
chaals@yandex-team.ru Find more at http://yandex.com
Received on Friday, 4 October 2013 01:05:16 UTC