Allow a #[gtest] test to specify a C++ class for its TestSuite.

By default the testing::Test class is used, which is equivalent to the
C++ TEST() macro. But just as in C++, with the TEST_F() macro, we need
a way to specify a different class to be the TestSuite. The only
requirement is that the test is a subclass of testing::Test.

We generalize the Gtest TestSuite factory code with a templated
function, but Rust can not call templated C++ functions yet. So we
still wrap that function with the pre-existing
rust_gtest_default_factory() function.

This would allow easily writing other factory functions in C++ targets
outside of //testing on top of the template helper, or even generating
such functions in the future.

We augment the #[gtest] macro to look for a further #[gtest_suite]
macro that names a C++ factory for the TestSuite class. The syntax is:

  #[gtest_suite(some_factory_function)]

Where the factory function is an unsafe extern "C" function pointer that
receives a function pointer and returns a
rust_gtest_interop::GtestFactoryPtr, making its signature:

  unsafe extern "C" fn(f: extern "C" fn()) -> GTestFactoryPtr

In the process, we drop a level of abstraction, so we no longer have a
factory-factory, and Rust works with a function pointer to the C++
function directly.

R=lukasza@chromium.org

Bug: 1305396
Change-Id: I1fe5efa8090435133054b3b7e71f28184b9d4733
Cq-Include-Trybots: luci.chromium.try:android-rust-arm-rel,android-rust-arm-dbg,linux-rust-x64-dbg,linux-rust-x64-rel
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3560902
Reviewed-by: Ɓukasz Anforowicz <lukasza@chromium.org>
Commit-Queue: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/main@{#987906}
10 files changed
tree: 13ac7714b9595794c17eb2ef751b189387342caf
  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/
  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. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython
  61. .vpython3
  62. .yapfignore
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. ENG_REVIEW_OWNERS
  70. LICENSE
  71. LICENSE.chromium_os
  72. OWNERS
  73. PRESUBMIT.py
  74. PRESUBMIT_test.py
  75. PRESUBMIT_test_mocks.py
  76. README.md
  77. 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.