Testing routing and navigation in Angular - Step-by-Step Execution

Concept Flow - Testing routing and navigation

Setup TestBed with RouterTestingModule

↓

Create component instance

↓

Trigger navigation action

↓

Router processes navigation

↓

Check current route and component

↓

Assert expected route and UI changes

↓

Test Pass/Fail

This flow shows how Angular tests routing by setting up a test environment, triggering navigation, and checking the results.

Execution Sample

Angular

import { TestBed } from '@angular/core/testing';
import { RouterTestingModule } from '@angular/router/testing';
import { Router } from '@angular/router';

// Setup TestBed with RouterTestingModule
// Trigger navigation and check current route

This code sets up Angular's test environment for routing, triggers navigation, and verifies the current route.

Execution Table

Step	Action	Router State Before	Navigation Triggered	Router State After	Assertion
1	Setup TestBed with RouterTestingModule	No router state	No	Router initialized	Router ready for navigation
2	Create component instance	Router initialized	No	Component created	Component ready
3	Trigger navigation to '/home'	At '/'	Yes	Navigating to '/home'	Navigation started
4	Router processes navigation	Navigating to '/home'	No	At '/home'	Route updated
5	Check current route	At '/home'	No	At '/home'	Route is '/home' as expected
6	Assert UI changes	At '/home'	No	UI updated for '/home'	UI matches route
7	Test completes	At '/home'	No	Test finished	Test passes

💡 Test ends after asserting the route and UI match expected '/home' path

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	Final
routerState	undefined	initialized	initialized	navigating to '/home'	at '/home'	at '/home'	at '/home'
componentInstance	undefined	undefined	created	created	created	created	created
navigationTriggered	false	false	false	true	false	false	false
uiState	initial	initial	initial	initial	updated for '/home'	updated for '/home'	updated for '/home'

Key Moments - 3 Insights

Why do we use RouterTestingModule instead of the real RouterModule?

RouterTestingModule provides a simplified router setup for tests without starting a real browser navigation, as shown in Step 1 of the execution_table.

What happens if we trigger navigation but don't wait for it to complete before asserting?

Assertions may fail because the router state hasn't updated yet. Step 4 shows the router processing navigation before assertions in Step 5.

How do we verify the UI matches the current route?

After navigation completes (Step 5), we check the UI updates accordingly (Step 6), ensuring the component reflects the route.

Visual Quiz - 3 Questions

Look at the execution_table, what is the routerState after Step 3?

A Navigating to '/home'

B At '/'

C At '/home'

D Router uninitialized

💡 Hint

Check the 'Router State After' column for Step 3 in the execution_table.

At which step does the test confirm the UI matches the route?

A Step 4

B Step 5

C Step 6

D Step 7

💡 Hint

Look for the step mentioning UI updates in the execution_table.

If navigation is not triggered at Step 3, what would be the routerState at Step 4?

A Navigating to '/home'

B At '/'

C At '/home'

D Router uninitialized

💡 Hint

Refer to the routerState changes in variable_tracker and execution_table rows 3 and 4.

Concept Snapshot

Testing routing in Angular:
- Use RouterTestingModule in TestBed
- Create component instance
- Trigger navigation with router.navigate()
- Wait for navigation to complete
- Assert current route and UI updates
- Ensures navigation works without real browser
- Helps catch routing bugs early

Full Transcript

This visual execution trace shows how Angular tests routing and navigation. First, the test environment is set up using RouterTestingModule to simulate routing without a real browser. Then, a component instance is created. Next, navigation is triggered to a specific route, such as '/home'. The router processes this navigation, updating its internal state. After navigation completes, the test checks the current route and verifies that the UI updates accordingly. Finally, assertions confirm the route and UI are as expected, and the test passes. This step-by-step flow helps beginners understand how routing tests work in Angular.