PersonalDataManagerTestBase -> PaymentsDataManagerTestBase

The class is currently used as the base class in three unittest files:
ADM unittest, PayDM unittest and PaymentsDataCleaner unittest.

Since payments has two separate databases (on disk + in memory), a lot
of the setup in PersonalDataManagerTestBase is unnecessary for ADM
purposes. Similarly, some of the logic (such as strike databases) is
exclusive to addresses. For this reason, this CL:
- Makes PersonalDataManagerTestBase::MakePrimaryAccountAvailable()
  a free function in personal_data_manager_test_utils.h. This is useful
  for all tests. Code moved without changes, except for introducing
  two parameters for fields that used to be members.
- Moves PersonalDataManagerTestBase::InitPersonalDataManager() to the
  PaymentsDataCleaner unittest, because it's only called there*.
- Moves address-relevant members of PersonalDataManagerTestBase to the
  ADM unittest and removes them from PersonalDataManagerTestBase.
- Renames PersonalDataManagerTestBase to PaymentsDataManagerTestBase and
  renames the file.

* Ideally, this test shouldn't depend on the PersonalDataManagerTestBase
  at all and instead just use the TestPayDM (like the AddressDataCleaner
  is using the TestADM). This hopefully happens in a follow-up, but I'm
  still experimenting with what the nices way to refactor that is. See
  crrev.com/c/5823218, for example.

Bug: 40100455
Change-Id: I7dbb99601a0b4453b364e699d3720de904f74223
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5823617
Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com>
Commit-Queue: Florian Leimgruber <fleimgruber@google.com>
Reviewed-by: Jihad Hanna <jihadghanna@google.com>
Cr-Commit-Position: refs/heads/main@{#1348684}
10 files changed
tree: 55b30cbe2dc78ad6a990e0ae6ed2b79b3ea8f4c7
  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.