Reland "Added a TestBidBuilder class create bids within tests."

This reverts commit 4f4a7664f17a1695ca905d13c1f018a498e0c83e.

Reason for revert: Edit to build file ensuring mojo_bindings are
built without depending on internals.

Original change's description:
> Revert "Added a TestBidBuilder class create bids within tests."
>
> This reverts commit d9c1a30d7b0b5f3e62a60bde571a83bc56d7778f.
>
> Reason for revert: This CL looks a cause of win-arm64-dbg compile failure. https://ci.chromium.org/ui/p/chromium/builders/ci/win-arm64-dbg/5830/overview
>
> Original change's description:
> > Added a TestBidBuilder class create bids within tests.
> >
> > Currently, each test that utilizes a bidder worklet bid constructs it
> > directly using the Bid constructor. This necessitates modifying over 170
> > test cases each time a new member is added to the Bid class.
> >
> > The TestBidBuilder provides a simple way of bid creation and reduces
> > code redundancy. This change ensures tests are less impacted by
> > redundancy. This change also ensures tests are less impacted by future
> > modifications to the Bid class and improves the overall readability
> > of the test suite.
> >
> > Change-Id: Ie722ba96c87bed71cc2bfa1c474f659ce21cefa3
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6102327
> > Reviewed-by: Maks Orlovich <morlovich@chromium.org>
> > Reviewed-by: Caleb Raitto <caraitto@chromium.org>
> > Commit-Queue: Youssef Bourouphael <ybourouphael@google.com>
> > Cr-Commit-Position: refs/heads/main@{#1406896}
>
> Change-Id: I676189b40ae7609463a21f815b7b865f221ff95e
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6169795
> Commit-Queue: Shunya Shishido <sisidovski@chromium.org>
> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
> Owners-Override: Shunya Shishido <sisidovski@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1407061}

Change-Id: I71ba20468c6b8a9cddb154d4018f4a787fd21ee5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6180097
Reviewed-by: Maks Orlovich <morlovich@chromium.org>
Reviewed-by: Caleb Raitto <caraitto@chromium.org>
Commit-Queue: Youssef Bourouphael <ybourouphael@google.com>
Cr-Commit-Position: refs/heads/main@{#1407894}
6 files changed
tree: 510d3c1a1ff4b35b7c1c9b970f78a296c96932c1
  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. gpu/
  24. headless/
  25. infra/
  26. ios/
  27. ipc/
  28. media/
  29. mojo/
  30. native_client_sdk/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. .clang-format
  50. .clang-tidy
  51. .clangd
  52. .git-blame-ignore-revs
  53. .gitallowed
  54. .gitattributes
  55. .gitignore
  56. .gitmodules
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. CPPLINT.cfg
  68. CRYPTO_OWNERS
  69. DEPS
  70. DIR_METADATA
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. 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.