Infrastrucutre for plumbing test hand joint data

Adds infrastructure to plumb hand joint data from tests into runtimes.
Unfortunately, this bumps the `ControllerFrameData` past the heuristic
where it is now "Complex" and needs explicit out-of-line constructor,
destructor, copy, and move operators. This in turn exposed some less-
than-ideal build configurations which are now cleaned up by way of a
new test hook component.

In order to decrease dependency on vr_service, XRHandJointData was moved
to its own mojom file as well. This uncovered an unneeded dependency
from vr_service onto browser_test_interfaces.mojom, which could now be
removed.

It does also appear that the vr_test_hook's usefulness is perhaps
somewhat questionable, as both the actual tests and test hook wrappers
translate from mojom types into test_hook types. We should really
investigate either typemapping or simply using the mojom types directly,
but attempting to do so quickly unveiled a lot of patterns that would
need to be cleaned up that were out of the scope of this CL, which is
aiming to add infrastructure to allow some basic tests that plumb up
hand joint data.

Bug: 359418633
Change-Id: Ib60f6c8ed9c420e481bb4d0d69ea30dc00f3374f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5847889
Reviewed-by: Matthew Denton <mpdenton@chromium.org>
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1356216}
14 files changed
tree: cd420f7e8b889f78b530d9aba9328ea0c451e6b0
  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. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. google_update/
  24. gpu/
  25. headless/
  26. infra/
  27. ios/
  28. ipc/
  29. media/
  30. mojo/
  31. native_client_sdk/
  32. net/
  33. pdf/
  34. ppapi/
  35. printing/
  36. remoting/
  37. rlz/
  38. sandbox/
  39. services/
  40. skia/
  41. sql/
  42. storage/
  43. styleguide/
  44. testing/
  45. third_party/
  46. tools/
  47. ui/
  48. url/
  49. webkit/
  50. .clang-format
  51. .clang-tidy
  52. .clangd
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitallowed
  56. .gitattributes
  57. .gitignore
  58. .gitmodules
  59. .gn
  60. .mailmap
  61. .rustfmt.toml
  62. .vpython3
  63. .yapfignore
  64. ATL_OWNERS
  65. AUTHORS
  66. BUILD.gn
  67. CODE_OF_CONDUCT.md
  68. codereview.settings
  69. CPPLINT.cfg
  70. CRYPTO_OWNERS
  71. DEPS
  72. DIR_METADATA
  73. LICENSE
  74. LICENSE.chromium_os
  75. OWNERS
  76. PRESUBMIT.py
  77. PRESUBMIT_test.py
  78. PRESUBMIT_test_mocks.py
  79. README.md
  80. 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.