Chrome Version: daec770ed8e9a12165629a75e2a30d192ea6865c
OS: Android
What steps will reproduce the problem?
(1) Try to create test using BackgroundTaskScheduler
What is the expected result?
It should be easy to write a test without mocking.
What happens instead?
It's hard, since you can't construct it easily.
Suggested fix:
- Rename BackgroundTaskScheduler to BackgroundTaskSchedulerImpl, and make BackgroundTaskSchedulerFactory create that instead.
- Create an interface BackgroundTaskScheduler that BackgroundTaskSchedulerImpl implements.
- Change the return type of BackgroundTaskSchedulerFactory#getScheduler() to be BackgroundTaskScheduler.
- Ensure that BackgroundTaskSchedulerDelegate and BackgroundTaskSchedulerImpl are package protected.
Comment 1 by bugdroid1@chromium.org
, Aug 16 2017