Component testing basics in Angular - Mini Project: Build & Apply

Component testing basics

📖 Scenario: You are building a simple Angular component that shows a greeting message. You want to write a basic test to check if the component renders the message correctly.

🎯 Goal: Create an Angular component called GreetingComponent that displays a greeting message. Then write a basic test to check if the message appears in the rendered output.

📋 What You'll Learn

Create a standalone Angular component named GreetingComponent

Add a string property message with the value 'Hello, Angular!'

Write a test that checks if the component renders the message text

Use Angular testing utilities and follow Angular 17+ standalone component patterns

💡 Why This Matters

🌍 Real World

Basic component testing is essential in Angular apps to ensure UI parts work as expected before releasing to users.

💼 Career

Frontend developers often write component tests to catch bugs early and maintain code quality in Angular projects.

1

Create the GreetingComponent with a message

Create a standalone Angular component called GreetingComponent. Inside it, define a public string property message and set it to 'Hello, Angular!'. Use the @Component decorator with a selector 'app-greeting' and a template that displays {{ message }}.

Angular

import { Component } from '@angular/core';

@Component({
  selector: 'app-greeting',
  standalone: true,
  template: `{{ message }}`
})
export class GreetingComponent {
  // Your code here
}

Hint

Use @Component with standalone: true. Define message as a public property with the exact string.

2

Set up the test environment for GreetingComponent

Create a test file for GreetingComponent. Import TestBed and ComponentFixture from @angular/core/testing. Configure the testing module with GreetingComponent as a standalone component. Declare variables fixture and component for the test setup.

Angular

import { TestBed, ComponentFixture } from '@angular/core/testing';

// Your code here

Hint

Use TestBed.configureTestingModule with imports array including GreetingComponent. Create fixture and component in beforeEach.

3

Write a test to check the rendered message

Inside the describe block, add an it test that calls fixture.detectChanges() and then checks if the rendered native element's text content includes the message property. Use expect and toContain for the assertion.

Angular

import { TestBed, ComponentFixture } from '@angular/core/testing';

describe('GreetingComponent', () => {
  let fixture: ComponentFixture;
  let component: GreetingComponent;

  beforeEach(() => {
    TestBed.configureTestingModule({
      imports: [GreetingComponent]
    });
    fixture = TestBed.createComponent(GreetingComponent);
    component = fixture.componentInstance;
  });

  // Add a test to check the rendered message
  // Your code here
});

Hint

Call fixture.detectChanges() before checking the DOM. Use fixture.nativeElement to access rendered HTML.

4

Complete the test file with necessary imports and exports

Ensure the test file imports Component from @angular/core and exports the GreetingComponent class. Confirm the test file has the full component and test code combined.

Angular

import { Component } from '@angular/core';
// Your code here

Hint

Make sure the component and test code are in the same file with proper imports and exports.

Practice

1. What is the main purpose of component testing in Angular?

easy

A. To test the entire application at once

B. To check if a component works correctly by itself

C. To test only the services used by components

D. To check the database connection

Solution

1. Step 1: Understand component testing scope

   Component testing focuses on testing a single component in isolation, not the whole app or services alone.

2. Step 2: Compare options with definition

   Only To check if a component works correctly by itself describes testing a component by itself, which matches the purpose of component testing.

3. Final Answer:

   To check if a component works correctly by itself -> Option B

4. Quick Check:

   Component testing = isolated component check [OK]

Hint: Component testing means testing one piece alone [OK]

Common Mistakes:

• Confusing component testing with full app testing
• Thinking services are tested alone in component tests
• Assuming database is tested in component tests

2. Which Angular testing utility is used to configure and create a component for testing?

easy

A. TestBed

B. HttpClient

C. NgModule

D. RouterModule

Solution

1. Step 1: Identify Angular testing utilities

   TestBed is the Angular utility designed to configure and create components in tests.

2. Step 2: Eliminate unrelated options

   HttpClient is for HTTP requests, NgModule defines modules, RouterModule handles routing, none create test components.

3. Final Answer:

   TestBed -> Option A

4. Quick Check:

   TestBed sets up test components [OK]

Hint: TestBed is the test setup tool in Angular [OK]

Common Mistakes:

• Confusing TestBed with NgModule
• Choosing HttpClient which is unrelated to testing setup
• Selecting RouterModule which is for routing

3. Given this test snippet, what will fixture.nativeElement.textContent contain?

TestBed.configureTestingModule({ declarations: [HelloComponent] }).compileComponents();
const fixture = TestBed.createComponent(HelloComponent);
fixture.componentInstance.name = 'Alice';
fixture.detectChanges();

@Component({ selector: 'app-hello', template: '<p>Hello, {{name}}!</p>' }) class HelloComponent { name = ''; }

medium

A. Hello, Alice!

B. Hello, !

C. Hello, name!

D. Error: name not defined

Solution

1. Step 1: Understand component property binding

   The component's name property is set to 'Alice' before change detection.

2. Step 2: Effect of fixture.detectChanges()

   This updates the template to reflect the new name value, so the paragraph shows 'Hello, Alice!'.

3. Final Answer:

   Hello, Alice! -> Option A

4. Quick Check:

   Property set + detectChanges updates template [OK]

Hint: detectChanges updates template with latest property values [OK]

Common Mistakes:

• Forgetting to call detectChanges so template stays old
• Assuming template shows variable name literally
• Thinking missing name causes error

4. What is wrong with this test setup code?

beforeEach(() => {
  TestBed.configureTestingModule({
    declarations: [MyComponent]
  });
  fixture = TestBed.createComponent(MyComponent);
  component = fixture.componentInstance;
});

medium

A. fixture and component should be declared inside beforeEach

B. Should import MyComponent instead of declaring it

C. Missing call to compileComponents() before createComponent()

D. No need to call createComponent() in beforeEach

Solution

1. Step 1: Check TestBed setup sequence

   When using TestBed with components, compileComponents() must be called to compile templates before creating the component.

2. Step 2: Identify missing step

   The code configures the module but skips compileComponents(), which can cause errors or incomplete setup.

3. Final Answer:

   Missing call to compileComponents() before createComponent() -> Option C

4. Quick Check:

   compileComponents() needed before createComponent() [OK]

Hint: Always call compileComponents() before createComponent() [OK]

Common Mistakes:

• Skipping compileComponents() causes template errors
• Declaring variables inside beforeEach unnecessarily
• Thinking createComponent() is optional

5. You want to test a component that shows a list of items passed as an input. Which approach correctly tests that the rendered list matches the input array?

@Component({ template: '<ul><li *ngFor="let item of items">{{item}}</li></ul>' })
class ListComponent { @Input() items: string[] = []; }

hard

A. Only check component.items property without inspecting the DOM

B. Set component.items but do not call detectChanges(), then check fixture.nativeElement.textContent

C. Call detectChanges() before setting component.items, then check component.items.length

D. Set component.items to an array, call detectChanges(), then check fixture.nativeElement.querySelectorAll('li').length

Solution

1. Step 1: Set input and update template

   Assign the input array to component.items and call detectChanges() to update the rendered list.

2. Step 2: Verify rendered list length

   Check the number of <li> elements in the DOM matches the input array length using querySelectorAll('li').length.

3. Final Answer:

   Set component.items, call detectChanges(), then check li elements count -> Option D

4. Quick Check:

   Input set + detectChanges + DOM check = correct test [OK]

Hint: Always call detectChanges() after input changes before checking DOM [OK]

Common Mistakes:

• Not calling detectChanges() after input change
• Checking component property only without DOM verification
• Calling detectChanges() before setting inputs