Reset PasswordManager in ReportMissingFormManager
The test PasswordManagerTest.ReportMissingFormManager executes a number of test-cases, and for each test-case, two runs, one with the old FormData parser, one with the new one. Each test-case can leave the PasswordManager in a state not expected by the next case, so it is good to reset the PasswordManager at the beginning of each run. This happens as part of setting the flags for the new parser automatically, but does not happen when the old parser is used. Thus, the tests failed if for each test-case the old parser was run first. This CL fixes that by ensuring that the PasswordManager is reset before each run. Bug: 907794 Change-Id: Id3ec0acf34d1a9d7b3530edd3eec0d6351fa4e1d Reviewed-on: https://chromium-review.googlesource.com/c/1350899 Commit-Queue: Vaclav Brozek <vabr@chromium.org> Reviewed-by:Vadym Doroshenko <dvadym@chromium.org> Cr-Commit-Position: refs/heads/master@{#611205}
Showing
Please register or sign in to comment