Mocking services in tests in Angular - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of mocking services in Angular tests?

Mocking services helps isolate the component or service being tested by replacing real dependencies with fake ones. This avoids side effects and makes tests faster and more reliable.

beginner

How do you create a simple mock service in Angular tests?

You create a class or object that implements the same methods as the real service but returns fixed or fake data instead of calling real APIs.

intermediate

What Angular testing utility helps replace a service with a mock in TestBed?

The TestBed.configureTestingModule method allows you to provide a mock service using the 'providers' array with { provide: RealService, useClass: MockService } or { provide: RealService, useValue: mockObject }.

beginner

Why is it important to use mocks instead of real services in unit tests?

Mocks prevent tests from depending on external systems, making tests faster, more predictable, and easier to run anywhere without setup.

intermediate

What is a spy in Angular testing and how does it relate to mocking services?

A spy is a special mock that tracks calls to methods and their arguments. It helps verify interactions with the service without running real code.

Which Angular testing method allows you to replace a real service with a mock?

A TestBed.configureTestingModule

B ComponentFixture.detectChanges

C NgModule.forRoot

D HttpClientModule

TestBed.configureTestingModule lets you provide mock services to replace real ones during testing.

What is the main benefit of mocking services in unit tests?

A More complex code

B Real API calls

C Faster and isolated tests

D Slower tests

Mocking services makes tests faster and isolates the tested code from external dependencies.

How can you create a mock service in Angular tests?

A By using Angular CLI commands

B By creating a class with the same methods returning fake data

C By calling the API directly

D By importing the real service

A mock service is a class or object that mimics the real service methods but returns fake data.

What does a spy do in Angular testing?

A Generates random data

B Runs the real service code

C Compiles the Angular app

D Tracks method calls and arguments

A spy monitors calls to methods and their arguments without executing real code.

Which of these is NOT a reason to mock services in tests?

A To make tests dependent on external APIs

B To speed up tests

C To avoid real network calls

D To isolate the tested component

Mocking services avoids dependency on external APIs, not making tests dependent on them.

Explain how to mock a service in Angular tests using TestBed.

Think about how Angular lets you swap real services with fake ones during testing.

Describe why mocking services is important for unit testing Angular components.

Consider what happens if tests call real servers or depend on external data.

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