At this point, we should be confident about performing the initial implementation of an Angular application using TDD. Also, we should be familiar with using the test-first approach. The test-first approach is very good for the learning stage, but sometimes it's a time suck when we get a lot of errors. For simple and known behavior, it may not be good to go for the test-first approach.
We have already seen how the test-first approach works, so we can skip those steps by checking any feature without creating those components. Besides that, we can go one step further to make us more confident in writing our components faster. We can have our components ready and then write end-to-end test specs to test the expected behavior. If the e2e test fails, we can trigger an error in the Protractor debugger.
In this chapter, we will continue to expand our knowledge of applying TDD (but not the test-first approach) with Angular. We will not discuss the details of the basic Angular...