Google Git
Sign in
chromium / chromium / src.git / f2fbeb7ad3ed97a57d60eb9635b7930842ce4cb3
commitf2fbeb7ad3ed97a57d60eb9635b7930842ce4cb3[log] [tgz]
authorAlan Screen <[email protected]>Sat Aug 28 05:27:38 2021
committerChromium LUCI CQ <[email protected]>Sat Aug 28 05:27:38 2021
tree104dbaaec7f18c486f7dacc16436c0a9a8942138
parentd1a0482edd387a742afd7bf859b465908705e971 [diff]
Introduce TestPrintingContext & test UpdatePrintSettings

Ability to test out-of-process print paths benefits from having a test
abstraction layer as close as possible to where the operating system
print APIs are made.  For printing this is primarily in two classes,
PrintBackend and PrintingContext.

Introduce a new TestPrintingContext class which is analogous to the
existing TestPrintBackend class.  This will support test scenarios for
printing a document, allowing for more testing coverage of the full
printing stack.

Start off with an implementation filled in for UpdatePrinterSettings(),
which is used at the start of the document printing pipeline.  This
enables testing to be introduced which provides coverage of
PrintJobWorker::UpdatePrintSettings() for Windows, macOS, and Linux.

Bug: 809738, 822505
Change-Id: Iee7b0be9e770226f88c6f1f834b4d01c5659a1d8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3058038
Commit-Queue: Alan Screen <[email protected]>
Reviewed-by: Lei Zhang <[email protected]>
Cr-Commit-Position: refs/heads/main@{#916218}
14 files changed
tree: 104dbaaec7f18c486f7dacc16436c0a9a8942138
  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. cloud_print/
  13. codelabs/
  14. components/
  15. content/
  16. courgette/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. jingle/
  32. media/
  33. mojo/
  34. native_client_sdk/
  35. net/
  36. pdf/
  37. ppapi/
  38. printing/
  39. remoting/
  40. rlz/
  41. sandbox/
  42. services/
  43. skia/
  44. sql/
  45. storage/
  46. styleguide/
  47. testing/
  48. third_party/
  49. tools/
  50. ui/
  51. url/
  52. weblayer/
  53. .clang-format
  54. .clang-tidy
  55. .eslintrc.js
  56. .git-blame-ignore-revs
  57. .gitattributes
  58. .gitignore
  59. .gn
  60. .mailmap
  61. .vpython
  62. .vpython3
  63. .yapfignore
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. ENG_REVIEW_OWNERS
  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.