@testing-library/angular

Find Similar Packages for @testing-library/angular

Package	Downloads	Stars	Size	Issues	Publish	License

@testing-library/angular	91,588	711	248 kB	8	a month ago	MIT

Simple and complete Angular testing utilities that encourage good testing practices.

Read The Docs | Edit the docs

TestingJavaScript.com Learn the smart, efficient way to test any JavaScript application.

The problem

You want to write maintainable tests for your Angular components. As a part of this goal, you want your tests to avoid including implementation details of your components and rather focus on making your tests give you the confidence for which they are intended. As part of this, you want your testbase to be maintainable in the long run so refactors of your components (changes to implementation but not functionality) don't break your tests and slow you and your team down.

This solution

The @testing-library/angular is a very lightweight solution for testing Angular components. It provides light utility functions on top of Angular and @testing-library/dom, in a way that encourages better testing practices. Its primary guiding principle is:

The more your tests resemble the way your software is used, the more confidence they can give you.

Example

counter.component.ts

@Component({
  selector: 'app-counter',
  template: `
    <span>{{ hello() }}</span>
    <button (click)="decrement()">-</button>
    <span>Current Count: {{ counter() }}</span>
    <button (click)="increment()">+</button>
  `,
})
export class CounterComponent {
  counter = model(0);
  hello = input('Hi', { alias: 'greeting' });

  increment() {
    this.counter.set(this.counter() + 1);
  }

  decrement() {
    this.counter.set(this.counter() - 1);
  }
}

counter.component.spec.ts

import { render, screen, fireEvent, aliasedInput } from '@testing-library/angular';
import { CounterComponent } from './counter.component';

describe('Counter', () => {
  it('should render counter', async () => {
    await render(CounterComponent, {
      inputs: {
        counter: 5,
        // aliases need to be specified this way
        ...aliasedInput('greeting', 'Hello Alias!'),
      },
    });

    expect(screen.getByText('Current Count: 5')).toBeVisible();
    expect(screen.getByText('Hello Alias!')).toBeVisible();
  });

  it('should increment the counter on click', async () => {
    await render(CounterComponent, { inputs: { counter: 5 } });

    const incrementButton = screen.getByRole('button', { name: '+' });
    fireEvent.click(incrementButton);

    expect(screen.getByText('Current Count: 6')).toBeVisible();
  });
});

See more examples

Installation

This module is distributed via npm which is bundled with node and should be installed as one of your project's devDependencies. Starting from ATL version 17, you also need to install @testing-library/dom:

npm install --save-dev @testing-library/angular @testing-library/dom

Or, you can use the ng add command. This sets up your project to use Angular Testing Library, which also includes the installation of @testing-library/dom.

ng add @testing-library/angular

You may also be interested in installing jest-dom so you can use the custom jest matchers.

Docs

Version compatibility

| Angular | Angular Testing Library | | ------- | ---------------------------- | | 18.x | 17.x, 16.x, 15.x, 14.x, 13.x | | 17.x | 17.x, 16.x, 15.x, 14.x, 13.x | | 16.x | 14.x, 13.x | | >= 15.1 | 14.x, 13.x | | < 15.1 | 12.x, 11.x | | 14.x | 12.x, 11.x |

Guiding Principles

The more your tests resemble the way your software is used, the more confidence they can give you.

We try to only expose methods and utilities that encourage you to write tests that closely resemble how your Angular components are used.

Utilities are included in this project based on the following guiding principles:

If it relates to rendering components, it deals with DOM nodes rather than component instances, nor should it encourage dealing with component instances.
It should be generally useful for testing individual Angular components or full Angular applications.
Utility implementations and APIs should be simple and flexible.

At the end of the day, what we want is for this library to be pretty light-weight, simple, and understandable.

Contributors

Thanks goes to these people (emoji key):

_{Tim Deschryver} 💻 📖 🚇 ⚠️	_{Michaël De Boey} 📖	_{Ignacio Le Fluk} 💻 ⚠️	_{Tamás Szabó} 💻	_{Gregor Woiwode} 💻	_{Toni Villena} 🐛 💻 📖 ⚠️	_ShPelles 📖
_Miluoshi 💻 ⚠️	_{Nick McCurdy} 📖	_{Srinivasan Sekar} 📖	_Bitcollage 📖	_{Emil Sundin} 💻	_Ombrax 💻	_{Rafael Santana} 💻 ⚠️ 🐛
_{Benjamin Blackwood} 📖 ⚠️	_{Gustavo Porto} 📖	_{Bo Vandersteene} 💻	_Janek 💻 ⚠️	_{Gleb Irovich} 💻 ⚠️	_Arjen 💻 🚧	_{Suguru Inatomi} 💻 🤔
_{Amit Miran} 🚇	_{Jan-Willem Willebrands} 💻	_Sandro 💻 🐛	_{Michael Westphal} 💻 ⚠️	_Lukas 💻	_{Matan Borenkraout} 🚧	_mleimer 📖 ⚠️
_MeIr 🐛 ⚠️	_{John Dengis} 💻 ⚠️	_{Rokas Brazdžionis} 💻	_{Mateus Duraes} 💻	_{Josh Joseph} 💻 ⚠️	_{Torsten Knauf} 🚧	_{antischematic} 🐛 🤔
_{Florian Pabst} 💻	_{Mark Goho} 🚧 📖	_{Jan-Willem Baart} 💻 ⚠️	_{S. Mumenthaler} 💻 ⚠️	_{Andrei Alecu} 💻 🤔 📖	_{Daniel Ramírez Barrientos} 💻	_{Mahdi Lazraq} 💻 ⚠️