Re-enable AccessibilityObjectModel tests by setting the status to "test".

Re-enable AccessibilityObjectModel tests by setting the status to "test".

By setting the status of the feature in RuntimeEnabledFeatures.json5 to "test"
instead of "experimental", it's automatically enabled in tests.

Previously when the mode was set to "experimental", it was being disabled
by the content feature.

If this is a reasonable fix, should we update the documentation at the top of
RuntimeEnabledFeatures.json5 to say that "test" can be used for features that
are controlled by a content flag but should be enabled for tests?

BUG=712332
Review-Url: https://codereview.chromium.org/2822313002
Cr-Commit-Position: refs/heads/master@{#465539}
Committed: https://chromium.googlesource.com/chromium/src/+/1c58631e4fa8074280e1ba81d639db80fcd5df3c

[dmazzoni, 2017-04-18 21:51:27]

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

[commit-bot: I haz the power, 2017-04-18 21:52:06]

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

[dmazzoni, 2017-04-18 21:55:57]

dmazzoni@chromium.org changed reviewers:
+ foolip@chromium.org, tkent@chromium.org

[tkent, 2017-04-18 23:10:01]

lgtm if test failures are resolved.

> If this is a reasonable fix, should we update the documentation at the top of
> RuntimeEnabledFeatures.json5 to say that "test" can be used for features that
> are controlled by a content flag but should be enabled for tests?

It sounds good.

[tkent, 2017-04-18 23:17:32]

> Previously when the mode was set to "experimental", it was being disabled
> by the content feature.

BTW, I think this behavior is still a bug. "experimental" and "test" should not
have any differences in layout tests.

[commit-bot: I haz the power, 2017-04-18 23:35:15]

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

[commit-bot: I haz the power, 2017-04-18 23:35:16]

Dry run: Try jobs failed on following builders:
  linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[dmazzoni, 2017-04-19 05:41:19]

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

[commit-bot: I haz the power, 2017-04-19 05:41:46]

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, 2017-04-19 07:21:09]

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

[commit-bot: I haz the power, 2017-04-19 07:21:10]

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_...)

[dmazzoni, 2017-04-19 07:34:18]

The CQ bit was checked by dmazzoni@chromium.org

[dmazzoni, 2017-04-19 07:34:18]

The patchset sent to the CQ was uploaded after l-g-t-m from tkent@chromium.org
Link to the patchset: https://codereview.chromium.org/2822313002/#ps40001
(title: "Update one more expectation")

[commit-bot: I haz the power, 2017-04-19 07:34:42]

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, 2017-04-19 09:26:33]

CQ is committing da patch.

Bot data: {"patchset_id": 40001, "attempt_start_ts": 1492587258532840,
"parent_rev": "8ac2349b4fc1649f4fef0a69de517ad74acabc10", "commit_rev":
"1c58631e4fa8074280e1ba81d639db80fcd5df3c"}

[commit-bot: I haz the power, 2017-04-19 09:26:46]

Description was changed from

==========
Re-enable AccessibilityObjectModel tests by setting the status to "test".

By setting the status of the feature in RuntimeEnabledFeatures.json5 to "test"
instead of "experimental", it's automatically enabled in tests.

Previously when the mode was set to "experimental", it was being disabled
by the content feature.

If this is a reasonable fix, should we update the documentation at the top of
RuntimeEnabledFeatures.json5 to say that "test" can be used for features that
are controlled by a content flag but should be enabled for tests?

BUG=712332
==========

to

==========
Re-enable AccessibilityObjectModel tests by setting the status to "test".

By setting the status of the feature in RuntimeEnabledFeatures.json5 to "test"
instead of "experimental", it's automatically enabled in tests.

Previously when the mode was set to "experimental", it was being disabled
by the content feature.

If this is a reasonable fix, should we update the documentation at the top of
RuntimeEnabledFeatures.json5 to say that "test" can be used for features that
are controlled by a content flag but should be enabled for tests?

BUG=712332

Review-Url: https://codereview.chromium.org/2822313002
Cr-Commit-Position: refs/heads/master@{#465539}
Committed:
https://chromium.googlesource.com/chromium/src/+/1c58631e4fa8074280e1ba81d639...
==========

[commit-bot: I haz the power, 2017-04-19 09:26:47]

Committed patchset #3 (id:40001) as
https://chromium.googlesource.com/chromium/src/+/1c58631e4fa8074280e1ba81d639...