chromium/src
0
Fork 0
Code Activity

[PDF OCR] Use an explicit value in PdfViewWebPluginTest

Browse Source 
Use an explicit value in testing, instead of hiding it in a variable.

AX-Relnotes: n/a.
Bug: 1393069
Change-Id: I9ef758751d79ccddb1df942cdfe48a66880e79b9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4501105
Reviewed-by: K. Moon <kmoon@chromium.org>
Commit-Queue: Kyungjun Lee <kyungjunlee@google.com>
Cr-Commit-Position: refs/heads/main@{#1139577}
This commit is contained in:
Kyungjun Lee
2023-05-04 16:09:01 +00:00
committed by Chromium LUCI CQ
parent 01fe460e90
commit 5e4fc04495
1 changed files with 1 additions and 3 deletions

4
pdf/pdf_view_web_plugin_unittest.cc

@ -885,9 +885,7 @@ TEST_F(PdfViewWebPluginTest,
plugin_->DocumentLoadComplete();
plugin_->LoadOrReloadAccessibility();
EXPECT_EQ(plugin_->next_accessibility_page_index_for_testing(), 0);
constexpr int32_t kPdfPageNum = 8;
plugin_->set_next_accessibility_page_index_for_testing(kPdfPageNum);
EXPECT_EQ(plugin_->next_accessibility_page_index_for_testing(), kPdfPageNum);
plugin_->set_next_accessibility_page_index_for_testing(5);
EXPECT_CALL(*accessibility_data_handler_ptr_, SetAccessibilityDocInfo);
plugin_->LoadOrReloadAccessibility();