Testing workflow

- [Instructor] As we've seen, by default … your tests are run on an actual Chrome instance. … In automated testing environments … where you don't need a visible UI, … it may be best to run your tests in a headless browser, … Chrome supports headless mode. … Which essentially means that you can run Chrome … without the UI show. … In the browsers array, … replace Chrome with ChromeHeadless, … let's go ahead and run ng test again. … Ng test--no-watch. … Our tests ran again … but this time using a headless instance of Chrome. … One of the benefits is that your test will be executed … in the same environment as users of your site. … It will also give you performance benefits … as you can run your tests in real browser context … without the memory overhead … of running a full instance of Chrome. … When running your test, you see a message here, … Executed 17 of 17. … But we don't know exactly which tests have run. … Let's go ahead and configure our terminal output. … We will first need to install a karma plugin, …