[BabelOrca] FakeSpeechRecognitionService supports multiple recognizers

Re-factors the Fake SpeechRecognitionService to support multiple
recognizers or AudioSourceFetchers.  This is done by re-factoring the
Service such that tests will assert against specific recognizers
instead of the service as a whole.

Justification for this re-factor comes from three sources:

1.) Since this test dependency is used in browser tests it should
behave as much like the real speech recognition service as possible.
This includes the fact that the real service can handle multiple
recognizers concurrently.

2.) In the next CL we will implement the majority of
go/babel-orca-mic-integration which modifies the
SystemLiveCaptionService.  In the new paradigm we want to be able
to test in an environment in which both versions of the
SystemLiveCaptionService are instantiated at the same time. see
the design for more information.

3.) In the future we plan on explicitly supporting mutliple
concurrent recognizers for LiveCaption.  In order to test behavior
there we have to ensure that tests can also support mutliple
concurrent recognizers.

DanglingUntriaged-notes: Adding new dangling pointers in tests only
AX-Relnotes: N/A
Design: go/babel-orca-mic-integration
Bug: N/A
Change-Id: I33353ead7a1dca48b630d9fd0e4386035ca63c2b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5664296
Reviewed-by: Devlin Cronin <rdevlin.cronin@chromium.org>
Reviewed-by: Evan Liu <evliu@google.com>
Reviewed-by: Ahmed Nasr <anasr@google.com>
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Katie Dektar <katie@chromium.org>
Commit-Queue: Avynn Donaghe <avynn@google.com>
Cr-Commit-Position: refs/heads/main@{#1346771}
16 files changed
tree: 0fdf10a7655ac8e99deb9699e372252c5aa97dd7
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. webkit/
  51. .clang-format
  52. .clang-tidy
  53. .clangd
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitallowed
  57. .gitattributes
  58. .gitignore
  59. .gitmodules
  60. .gn
  61. .mailmap
  62. .rustfmt.toml
  63. .vpython3
  64. .yapfignore
  65. ATL_OWNERS
  66. AUTHORS
  67. BUILD.gn
  68. CODE_OF_CONDUCT.md
  69. codereview.settings
  70. CPPLINT.cfg
  71. CRYPTO_OWNERS
  72. DEPS
  73. DIR_METADATA
  74. LICENSE
  75. LICENSE.chromium_os
  76. OWNERS
  77. PRESUBMIT.py
  78. PRESUBMIT_test.py
  79. PRESUBMIT_test_mocks.py
  80. README.md
  81. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure.

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.