To avoid maintaining complex mocks, I would suggest to keep the mock as simple as possible. As there are sufficient unit tests for `SettingsService`, we can ensure that everything is good when `navigate` is called. Hence in most of the tests we can simply check if `navigate` is called with correct parameters rather than check the result in `SettingsService`.