Mocking services in tests in Angular - Step-by-Step Execution

Concept Flow - Mocking services in tests

Test Setup

↓

Create Mock Service

↓

Inject Mock into Component

↓

Run Test

↓

Verify Behavior

↓

Test Pass/Fail

This flow shows how a mock service replaces a real service in tests to control behavior and verify outcomes.

Execution Sample

Angular

import { TestBed } from '@angular/core/testing';
import { MyComponent } from './my.component';
import { DataService } from './data.service';

const mockDataService = { getData: () => ['mock', 'data'] };

TestBed.configureTestingModule({
  providers: [{ provide: DataService, useValue: mockDataService }]
});

This code sets up a test where DataService is replaced by a mock that returns fixed data.

Execution Table

Step	Action	Service Used	Component Behavior	Test Outcome
1	TestBed configures testing module	Mock service created	Component will use mock service	Setup ready
2	Component created and injected	Mock service injected	Component calls getData() on mock	Mock data returned ['mock', 'data']
3	Component processes data	Mock service data used	Component displays or uses mock data	Behavior controlled by mock
4	Assertions run	Mock service data verified	Test checks expected output from mock data	Test passes if output matches
5	Test completes	Mock service only used	No real service calls made	Test isolated and reliable

💡 Test ends after assertions verify component behavior using mock service data

Variable Tracker

Variable	Start	After Setup	After Injection	After Data Call	Final
dataService	undefined	mockDataService object	mockDataService object	mockDataService.getData() returns ['mock', 'data']	mockDataService object
componentData	undefined	undefined	undefined	['mock', 'data']	['mock', 'data']

Key Moments - 3 Insights

Why does the component use the mock service instead of the real one?

Because in TestBed configuration, the real service is replaced by the mock using provide/useValue, as shown in execution_table step 1.

How does the mock service control the test outcome?

The mock returns fixed data, so the component behavior is predictable and test assertions can verify expected results, as seen in steps 3 and 4.

What happens if we forget to provide the mock service in the test setup?

The component would use the real service, possibly causing unpredictable behavior or external calls, breaking test isolation (not shown in the table but implied).

Visual Quiz - 3 Questions

Look at the execution table, at which step is the mock service injected into the component?

A Step 3

B Step 1

C Step 2

D Step 4

💡 Hint

Check the 'Service Used' and 'Action' columns in execution_table row for Step 2.

According to variable_tracker, what is the value of componentData after the data call?

A undefined

B ['mock', 'data']

C null

D empty array []

💡 Hint

Look at the 'componentData' row under 'After Data Call' column in variable_tracker.

If the mock service returned an empty array instead, how would the test outcome in step 4 change?

A Test would fail if expecting ['mock', 'data']

B Test would pass regardless

C Test would error out

D No change in test outcome

💡 Hint

Refer to execution_table step 4 where assertions check expected output from mock data.

Concept Snapshot

Mocking services in Angular tests:
- Use TestBed to replace real service with mock via provide/useValue
- Mock controls data returned to component
- Component uses mock service during test
- Assertions verify behavior based on mock data
- Ensures isolated, predictable tests

Full Transcript

In Angular testing, mocking services means replacing a real service with a fake one that returns controlled data. The test setup uses TestBed to provide the mock service instead of the real one. When the component is created, it receives the mock service. The component calls methods on the mock, which returns fixed data. This predictable data lets tests check if the component behaves correctly. The test ends after assertions confirm the expected behavior. This approach avoids real service calls and makes tests reliable and isolated.

Practice

1. What is the main purpose of mocking services in Angular tests?

easy

A. To automatically generate service code

B. To speed up the Angular application in production

C. To add new features to the service during testing

D. To replace real services with fake ones for isolated testing

Solution

1. Step 1: Understand the role of mocking

   Mocking replaces real dependencies with controlled fake versions to isolate the component under test.

2. Step 2: Identify the testing benefit

   This isolation helps tests run faster and more reliably without depending on real service behavior.

3. Final Answer:

   To replace real services with fake ones for isolated testing -> Option D

4. Quick Check:

   Mocking = Replace real with fake [OK]

Hint: Mocking means replacing real services with fakes in tests [OK]

Common Mistakes:

• Thinking mocking speeds up production app
• Confusing mocking with adding features
• Believing mocking auto-generates code

2. Which syntax correctly provides a mock service using useClass in Angular test setup?

easy

A. providers: [{ provide: RealService, useClass: MockService }]

B. providers: [{ useClass: RealService, provide: MockService }]

C. providers: [{ provide: MockService, useClass: RealService }]

D. providers: [{ useValue: MockService, provide: RealService }]

Solution

1. Step 1: Recall Angular provider syntax

   Angular expects an object with 'provide' as the token and 'useClass' as the mock class.

2. Step 2: Match correct order and keys

   The correct order is 'provide' first, then 'useClass' with the mock class.

3. Final Answer:

   providers: [{ provide: RealService, useClass: MockService }] -> Option A

4. Quick Check:

   Provide token, then useClass mock [OK]

Hint: Remember: provide token first, then useClass mock class [OK]

Common Mistakes:

• Swapping provide and useClass keys
• Using useValue instead of useClass incorrectly
• Providing mock as token instead of real service

3. Given this Angular test setup, what will component.getData() return?

class MockService {
  fetch() { return 'mocked data'; }
}

TestBed.configureTestingModule({
  providers: [{ provide: RealService, useClass: MockService }]
});

const service = TestBed.inject(RealService);
const component = new MyComponent(service);

component.getData = function() { return this.service.fetch(); };

medium

A. undefined

B. 'real data'

C. 'mocked data'

D. Throws runtime error

Solution

1. Step 1: Identify the injected service

   The test replaces RealService with MockService using useClass, so service is an instance of MockService.

2. Step 2: Trace method call in component

   component.getData calls service.fetch(), which returns 'mocked data' from MockService.

3. Final Answer:

   'mocked data' -> Option C

4. Quick Check:

   MockService fetch() returns 'mocked data' [OK]

Hint: Injected service is mock, so method returns mock's value [OK]

Common Mistakes:

• Assuming real service is used
• Expecting undefined instead of mock return
• Thinking method throws error without real service

4. What is wrong with this Angular test provider setup?

providers: [{ provide: RealService, useValue: MockService }]

medium

A. Missing import for RealService

B. useValue expects an instance, not a class reference

C. useValue cannot be used in providers

D. provide should be MockService, not RealService

Solution

1. Step 1: Understand useValue usage

   useValue expects an actual instance or object, not a class reference.

2. Step 2: Identify the mistake

   MockService is a class, but useValue is given the class itself, not an instance like new MockService().

3. Final Answer:

   useValue expects an instance, not a class reference -> Option B

4. Quick Check:

   useValue needs instance, not class [OK]

Hint: useValue needs instance (new), not class name [OK]

Common Mistakes:

• Passing class instead of instance to useValue
• Confusing provide token with mock class
• Assuming useValue can't be used in providers

5. You want to mock a service method that returns different values on consecutive calls in Angular tests. Which approach correctly achieves this?

hard

A. Create a mock class with a method using a call count variable to return different values

B. Use useValue with a plain object having the method returning a fixed value

C. Use useClass with the real service and override the method in the test

D. Inject the real service and spy on the method without mocking

Solution

1. Step 1: Understand requirement for different returns

   Returning different values on consecutive calls requires state tracking inside the mock method.

2. Step 2: Choose correct mocking approach

   A mock class with a call count variable can track calls and return different values accordingly.

3. Step 3: Evaluate other options

   useValue with fixed return can't vary returns; overriding real service method is complex; spying alone doesn't mock service.

4. Final Answer:

   Create a mock class with a method using a call count variable to return different values -> Option A

5. Quick Check:

   Mock class with state tracks calls for varied returns [OK]

Hint: Use mock class with call count to vary method returns [OK]

Common Mistakes:

• Using fixed return object for varying outputs
• Overriding real service instead of mocking
• Relying only on spies without mocks