DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’»

DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’» is a community of 966,904 amazing developers

We're a place where coders share, stay up-to-date and grow their careers.

Create account Log in
Cover image for Simplifying Angular testbed setup by converting to synchronous test hooks
Lars Gyrup Brink Nielsen for This is Angular

Posted on • Updated on

Simplifying Angular testbed setup by converting to synchronous test hooks

When we use Angular's schematics to generate components, unnecessary asynchronous code is added to the test setup hook for its test suite.

The following test setup is generated by Angular's component generation schematic:

beforeEach(async () => {
  await TestBed.configureTestingModule({
    declarations: [MyComponent],
  }).compileComponents();
});
Enter fullscreen mode Exit fullscreen mode
Angular testbed setup generated by the component schematic.

Alternatively, we might be using Angular's waitForAsync test function wrapper (formerly named async) as seen in the following code snippet:

beforeEach(waitForAsync(() => {
  TestBed.configureTestingModule({
    declarations: [MyComponent],
  }).compileComponents();
}));
Enter fullscreen mode Exit fullscreen mode
Angular testbed setup using waitForAsync.

Here's the deal: It's only necessary to call the static TestBed.compileComponents method if we're not using the Angular CLI to run our tests (who would do such a thing, Google? πŸ‘ˆπŸ˜).

The Angular CLI compiles our application and tests before the tests are run so no asynchronous action is needed for setting up the declarables.

Let's simplify the common test setup by leaving out async-await, waitForAsync, and even the TestBed.compileComponents invocation as seen in this code snippet:

beforeEach(() => {
  TestBed.configureTestingModule({
    declarations: [MyComponent],
  });
});
Enter fullscreen mode Exit fullscreen mode
Simplified Angular testbed setup.

The following points are true for common Angular testbed setup for tests covering all types of Angular declarables:

  • No need to use async-await
  • No need to use waitForAsync (formerly named async)
  • No need to call TestBed.compileComponents

Of course, there might be other reasons for introducing asynchronicity to our test setup but compiling and linking declarables is not one of them.

Enjoy a little less boilerplate in your Angular tests 🌞

Top comments (1)

Collapse
 
dylanwatsonsoftware profile image
Dylan Watson

I haven't given it a go yet.. but if that's true that'll be a big win! Nice!

🌚 Browsing with dark mode makes you a better developer.

It's a scientific fact.