I see three more I'd like to take care of:
* AutofillManagerTest's MockAutofillDriver extends TestAutofillDriver but adds a small amount of additional logic as well. The logic it adds should really just go in TestAutofillDriver, so the Mock implementation is purely just mocking the test class.
* Ditto for TestAutofillDownloadManager. It's used only in AutofillManagerTest, but it mocks some methods despite not being named MockAutofillDownloadManager. Other instances of this pattern in the area delegate the logic to the test class, then mock the test class.
* TestAutofillExternalDelegate is implemented by both AutofillManagerTest and AutofillPopupControllerBrowserTest, so that's the last one that appears to be duplicated in multiple places.
Comment 1 by jsaul@google.com
, Dec 6 2017