Explicitly skip notification announcements in SpokenFeedbackTest

Explicitly skip notification announcements in SpokenFeedbackTest

Since ChromeVox Next behaves slightly differently (it is more aggressive about placing initial focus), there are a lot more utterances that can occur on startup. In addition, it triggers a notification center alert which also causes output.

This cl skips those messages explicitly.

Also, disable
TypeInOmniBox
because on slower debug builds, it appears we're actually prepending when typing to about:blank.
NavigateNotificationCenter
This test is super brittle because it relies on the "Button" utterance to trigger tabbing.

In general, most of these tests are brittle because they rely upon a strict ordering of utterances with no tolerance for various UI events. This should be solved later hopefully with the js-based tests in chrome/browser/resources/chromeos/chromevox/cvox2/background/background_test.extjs as an example.

BUG=659181
TBR=dmazzoni@chromium.org

Committed: https://crrev.com/f66eb9d5822ec392f9b7262cf3662924e80b0b93
Cr-Commit-Position: refs/heads/master@{#427444}

[David Tseng, 2016-10-25 19:15:19]

Description was changed from

==========
Explicitly skip notification announcements in SpokenFeedbackTest

Since ChromeVox Next behaves slightly differently (it is more aggressive about
placing initial focus), there are a lot more utterances that can occur on
startup. In addition, it triggers a notification center alert which also causes
output.

This cl skips those messages explicitly.

Also, disable
TypeInOmniBox
because on slower debug builds, it appears we're actually prepending when typing
to about:blank.
NavigateNotificationCenter
This test is super brittle because it relies on the "Button" utterance to
trigger tabbing.

In general, most of these tests are brittle because they rely upon a strict
ordering of utterances with no tolerance for various UI events. This should be
solved later hopefully with the js-based tests in
chrome/browser/resources/chromeos/chromevox/cvox2/background/background_test.extjs
as an example.

BUG=
TBR=dmazzoni@chromium.org
==========

to

==========
Explicitly skip notification announcements in SpokenFeedbackTest

Since ChromeVox Next behaves slightly differently (it is more aggressive about
placing initial focus), there are a lot more utterances that can occur on
startup. In addition, it triggers a notification center alert which also causes
output.

This cl skips those messages explicitly.

Also, disable
TypeInOmniBox
because on slower debug builds, it appears we're actually prepending when typing
to about:blank.
NavigateNotificationCenter
This test is super brittle because it relies on the "Button" utterance to
trigger tabbing.

In general, most of these tests are brittle because they rely upon a strict
ordering of utterances with no tolerance for various UI events. This should be
solved later hopefully with the js-based tests in
chrome/browser/resources/chromeos/chromevox/cvox2/background/background_test.extjs
as an example.

BUG=659181
TBR=dmazzoni@chromium.org
==========

[David Tseng, 2016-10-25 19:15:36]

The CQ bit was checked by dtseng@chromium.org

[commit-bot: I haz the power, 2016-10-25 19:15:54]

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-10-25 19:45:30]

Description was changed from

==========
Explicitly skip notification announcements in SpokenFeedbackTest

Since ChromeVox Next behaves slightly differently (it is more aggressive about
placing initial focus), there are a lot more utterances that can occur on
startup. In addition, it triggers a notification center alert which also causes
output.

This cl skips those messages explicitly.

Also, disable
TypeInOmniBox
because on slower debug builds, it appears we're actually prepending when typing
to about:blank.
NavigateNotificationCenter
This test is super brittle because it relies on the "Button" utterance to
trigger tabbing.

In general, most of these tests are brittle because they rely upon a strict
ordering of utterances with no tolerance for various UI events. This should be
solved later hopefully with the js-based tests in
chrome/browser/resources/chromeos/chromevox/cvox2/background/background_test.extjs
as an example.

BUG=659181
TBR=dmazzoni@chromium.org
==========

to

==========
Explicitly skip notification announcements in SpokenFeedbackTest

Since ChromeVox Next behaves slightly differently (it is more aggressive about
placing initial focus), there are a lot more utterances that can occur on
startup. In addition, it triggers a notification center alert which also causes
output.

This cl skips those messages explicitly.

Also, disable
TypeInOmniBox
because on slower debug builds, it appears we're actually prepending when typing
to about:blank.
NavigateNotificationCenter
This test is super brittle because it relies on the "Button" utterance to
trigger tabbing.

In general, most of these tests are brittle because they rely upon a strict
ordering of utterances with no tolerance for various UI events. This should be
solved later hopefully with the js-based tests in
chrome/browser/resources/chromeos/chromevox/cvox2/background/background_test.extjs
as an example.

BUG=659181
TBR=dmazzoni@chromium.org
==========

[commit-bot: I haz the power, 2016-10-25 19:45:31]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-10-25 20:00:10]

Description was changed from

==========
Explicitly skip notification announcements in SpokenFeedbackTest

Since ChromeVox Next behaves slightly differently (it is more aggressive about
placing initial focus), there are a lot more utterances that can occur on
startup. In addition, it triggers a notification center alert which also causes
output.

This cl skips those messages explicitly.

Also, disable
TypeInOmniBox
because on slower debug builds, it appears we're actually prepending when typing
to about:blank.
NavigateNotificationCenter
This test is super brittle because it relies on the "Button" utterance to
trigger tabbing.

In general, most of these tests are brittle because they rely upon a strict
ordering of utterances with no tolerance for various UI events. This should be
solved later hopefully with the js-based tests in
chrome/browser/resources/chromeos/chromevox/cvox2/background/background_test.extjs
as an example.

BUG=659181
TBR=dmazzoni@chromium.org
==========

to

==========
Explicitly skip notification announcements in SpokenFeedbackTest

Since ChromeVox Next behaves slightly differently (it is more aggressive about
placing initial focus), there are a lot more utterances that can occur on
startup. In addition, it triggers a notification center alert which also causes
output.

This cl skips those messages explicitly.

Also, disable
TypeInOmniBox
because on slower debug builds, it appears we're actually prepending when typing
to about:blank.
NavigateNotificationCenter
This test is super brittle because it relies on the "Button" utterance to
trigger tabbing.

In general, most of these tests are brittle because they rely upon a strict
ordering of utterances with no tolerance for various UI events. This should be
solved later hopefully with the js-based tests in
chrome/browser/resources/chromeos/chromevox/cvox2/background/background_test.extjs
as an example.

BUG=659181
TBR=dmazzoni@chromium.org

Committed: https://crrev.com/f66eb9d5822ec392f9b7262cf3662924e80b0b93
Cr-Commit-Position: refs/heads/master@{#427444}
==========

[commit-bot: I haz the power, 2016-10-25 20:00:11]

Patchset 1 (id:??) landed as
https://crrev.com/f66eb9d5822ec392f9b7262cf3662924e80b0b93
Cr-Commit-Position: refs/heads/master@{#427444}