Automate Fullscreen web-platform-tests using wpt_automation

Automate Fullscreen web-platform-tests using wpt_automation

BUG=660846
Committed: https://crrev.com/529fd9c41df97f26fd8e3ff26222f3ae195365d6
Cr-Commit-Position: refs/heads/master@{#429118}

[foolip, 2016-11-01 13:15:15]

foolip@chromium.org changed reviewers:
+ rbyers@chromium.org

[foolip, 2016-11-01 13:15:15]

PTAL. I'm quite skeptical that the wpt_automation approach will scale, but
having shared manual tests is slightly better than nothing when it gets to
shipping unprefixed Fullscreen.

[foolip, 2016-11-01 13:15:21]

The CQ bit was checked by foolip@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-11-01 13:15:27]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-11-01 14:15:10]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-11-01 14:15:11]

Dry run: Try jobs failed on following builders:
  win_chromium_rel_ng on master.tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[eae, 2016-11-01 16:11:55]

eae@chromium.org changed reviewers:
+ eae@chromium.org

[eae, 2016-11-01 16:11:56]

OK, let's try it.

LGTM

[Rick Byers, 2016-11-01 20:29:10]

LGTM
I'll be interested to hear how this works out.  I'm anxious to have standard
automation also, but hopeful we can get by with hacks like this for now...

[foolip, 2016-11-01 20:32:48]

The CQ bit was checked by foolip@chromium.org

[foolip, 2016-11-01 20:32:48]

The patchset sent to the CQ was uploaded after l-g-t-m from eae@chromium.org,
rbyers@chromium.org
Link to the patchset: https://codereview.chromium.org/2466333002/#ps20001
(title: "update line numbers")

[commit-bot: I haz the power, 2016-11-01 20:34:12]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[foolip, 2016-11-01 20:37:02]

On 2016/11/01 20:29:10, Rick Byers wrote:
> LGTM
> I'll be interested to hear how this works out.  I'm anxious to have standard
> automation also, but hopeful we can get by with hacks like this for now...

I think this specific tests, and those previously automated with wpt_automation,
will be fine. My concern is more that the overhead is such that it won't get
done for a feature where just a test or two need user gestures, and also that
there's no way that one vendor can write a test that semi-automatically gets run
(correctly) by others with this setup.

Fortunately, these tests are about as simple as it gets with regards to input,
basically any input automation API, however limited, should cover this.

[commit-bot: I haz the power, 2016-11-01 21:34:53]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-11-01 21:39:37]

Description was changed from

==========
Automate Fullscreen web-platform-tests using wpt_automation

BUG=660846
==========

to

==========
Automate Fullscreen web-platform-tests using wpt_automation

BUG=660846

Committed: https://crrev.com/529fd9c41df97f26fd8e3ff26222f3ae195365d6
Cr-Commit-Position: refs/heads/master@{#429118}
==========

[commit-bot: I haz the power, 2016-11-01 21:39:38]

Patchset 2 (id:??) landed as
https://crrev.com/529fd9c41df97f26fd8e3ff26222f3ae195365d6
Cr-Commit-Position: refs/heads/master@{#429118}