Service locator pattern in Flutter - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding the purpose of the Service Locator pattern

What is the main benefit of using the Service Locator pattern in Flutter app testing?

A It replaces the need for unit tests by providing integration tests only.

B It automatically generates UI tests without writing code.

C It centralizes the creation and access of services, making it easier to swap implementations during tests.

D It enforces strict type checking at compile time for all services.

💡 Hint

Think about how managing dependencies helps testing.

The Service Locator pattern centralizes service management, allowing easy replacement of real services with mocks or fakes during testing.

❓ Predict Output

intermediate

Output of service locator registration and retrieval

Given the following Flutter service locator code snippet, what will be printed?

Flutter

final locator = ServiceLocator();

class ApiService {
  String fetchData() => 'Real Data';
}

void main() {
  locator.register<ApiService>(ApiService());
  final api = locator.get<ApiService>();
  print(api.fetchData());
}

A Throws an exception: Service not found

B Real Data

C null

D Instance of 'ApiService'

💡 Hint

Check what fetchData() returns and what is printed.

The ApiService is registered and retrieved correctly, so calling fetchData() returns 'Real Data' which is printed.

❓ assertion

advanced

Correct assertion for mocked service call

In a Flutter test using a service locator, which assertion correctly verifies that the mocked ApiService's fetchData method returns 'Mock Data'?

Flutter

class MockApiService extends Mock implements ApiService {}

void main() {
  final mockApi = MockApiService();
  when(() => mockApi.fetchData()).thenReturn('Mock Data');
  locator.register<ApiService>(mockApi);
  final api = locator.get<ApiService>();
  final result = api.fetchData();
  // Which assertion below is correct?
}

A expect(result, equals('Mock Data'));

B expect(result, isNull);

C expect(result, equals('Real Data'));

D expect(result, isNotEmpty);

💡 Hint

Check what the mock returns and what the assertion compares.

The mock is set to return 'Mock Data', so the assertion must check that result equals 'Mock Data'.

🔧 Debug

advanced

Debugging service locator registration error

Why does the following Flutter test code throw an exception when trying to retrieve a service?

Flutter

final locator = ServiceLocator();

class ApiService {}

void main() {
  final api = locator.get<ApiService>();
  print(api);
}

A Because ApiService was never registered before calling get, causing a 'Service not found' error.

B Because locator.get requires an async call which is missing.

C Because ApiService class is missing a default constructor.

D Because print cannot output class instances directly.

💡 Hint

Check if the service was registered before retrieval.

The error occurs because the service locator has no registered instance of ApiService when get is called.

❓ framework

expert

Best practice for resetting service locator in Flutter tests

In Flutter testing, what is the best way to ensure the service locator is clean before each test to avoid state leakage?

A Do nothing; service locator state does not affect tests.

B Create a new service locator instance inside each test without resetting.

C Rely on Flutter's hot reload to clear the locator state automatically.

D Call locator.reset() or equivalent method in the setUp() function before each test.

💡 Hint

Think about test isolation and shared state.

Resetting the service locator before each test ensures no leftover services interfere with other tests, maintaining isolation.