SurfaceFactory is no longer really a factory of surfaces because SurfaceManager manages the lifetime of surfaces.
Now that we've replaced all usage of SurfaceFactory with CompositorFrameSinkSupport, we should move all functionality in SurfaceFactory out to CompositorFrameSinkSupport and delete SurfaceFactory at this point.
As a first step, we probably want to port all tests over to CompositorFrameSinkSupport. FakeSurfaceFactoryClient should change to be a CompositorFrameSinkSupport I suppose.
surface_unittest.cc uses a SurfaceFactory with a FakeSurfaceFactoryClient. The test requires SurfaceFactory::SubmitCompositorFrame and EvictFrame. I think we need a FakeCompositorFrameSinkSupportClient instead of a FakeCompositorFrameSinkSupport.
I'm working on surface_aggregator_unittest now, which is similar. I'm thinking to put FakeCompositorFrameSinkSupportClient into its own files or some test util files so that we don't have to write one for each test that's using it.
Comment 1 by fsam...@chromium.org
, Apr 1 2017