Therefore, we can safely remove anything related to Jasmine. We're already living in heaven and may be using Cypress later. Moreover, I assume that we won't use Protractor as E2E testing framework. This guide assumes that you are using Angular in version 8 (as it uses the new CLI builders). At this point you should think about using the great debugging features of your editor. The debug logs would spam the terminal and you will probably have to scroll a lot to find the outputs you are looking for. Since Jest is headless which means that it won't spawn a browser window where you can open Chrome Dev Tools, it can get cumbersome to use console-logs when trying to debug while testing. In my opinion it has some advantages over the default setup: It is headless out-of-the-box, less configuration is needed and it has some handy features like snapshot testing. In recent times I often prefer Jest as testing framework. The default test runner for Angular applications is Karma in combination with Jasmine as test framework. My goal is to describe everything that is needed in one single post.

The upcoming information is already present online but varies and is distributed over several sources *. However, I myself will surely read my own as long as I haven't completely automated the following steps. I always thought that no one will ever read my blog posts. This article aims to describe a really fast step-by-step way to setup Jest testing for Angular projects including debugging capabilities of Visual Studio Code.

Visual studio code debug tests